Skip to content

chore: sync master version metadata to v0.1.192 (Release drift guard) - #2765

Merged
ranxianglei merged 1 commit into
masterfrom
2026-10-11_sync-master-v0.1.192
Oct 11, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-10-11_sync-master-v0.1.192

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Why

The one-click Release workflow run 38133050838 (target 0.1.193) failed at the Drift guard:

::error::master package.json (0.1.191) != npm latest (0.1.192).
Sync master with the last published release before one-click releasing.

v0.1.192 was a carve-out release (78df4eaa, #2664 only, on top of v0.1.191) and its version bump never flowed back to master — unlike v0.1.191, which was synced via #2630.

What

Metadata-only bump 0.1.191 → 0.1.192:

  • package.json
  • package-lock.json (root version + packages."".version)

#2664's code changes are already in master via f0b3f5d6, so master is content-wise a superset of v0.1.192; nothing but the version fields was stale. Precedent: aeac5a8.

After merge

Re-dispatch Release (one-click) with target 0.1.193 — that release will carry the #2755 fold-summary head-stability fix (kernel 0.0.116).

kernel-change: none

v0.1.192 was a carve-out release (78df4ea, #2664 only) and its version
bump never flowed back to master, so master still declares 0.1.191 while
npm latest is 0.1.192. That trips the Release one-click Drift guard:

  ::error::master package.json (0.1.191) != npm latest (0.1.192)

#2664's changes themselves are already in master (f0b3f5d), so this is
metadata-only: bump package.json + package-lock.json (root and
packages."" entries) to 0.1.192 so the next one-click release (0.1.193,
carrying the #2755 fold-summary head-stability fix) can proceed.
@ranxianglei
ranxianglei merged commit 9dd4a36 into master Oct 11, 2026
24 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-11_sync-master-v0.1.192 (3e5a449)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.3038-pr.2765.1b1b950

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr2765.tgz
npm install -g package

Install instructions are refreshed on each push.

@github-actions

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.276-master.9dd4a36 (rolling master tag).

npm install -g billion-context@0.0.276-master.9dd4a36  # this exact build
npm install -g billion-context@master  # always the newest merged build

npm view billion-context@master prints the current version at any time.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 已核实:此同步已完成并合入 master,无需再动。 Drift guard 现在会通过,可以直接 re-dispatch。

核实证据(全部实测):

结构化八问:

  1. 是什么问题:carve-out 发布(v0.1.192,仅含 fix(#2658): dsh native-compaction rebase fallback on anthropic/google lanes #2664)的版本号没有回流到 master,master 仍声明 0.1.191,与 npm latest 0.1.192 不一致,卡住 one-click release 的 Drift guard。
  2. 什么原因导致的:bili 0.1.181:clampOutputBudget 把小数写进 max_tokens,上游 400 max_tokens: Input should be a valid integer / 422 Endpoint is unavailable #2011 carve-out 通道(dispatch 触发、无 release 分支)只发布不回写 master 的版本字段,与常规 release 分支流程(版本号随 merge 自然回流)不同步。
  3. 影响范围与严重程度:仅阻塞下一次 one-click release(0.1.193);对已部署用户零影响。现已解除。
  4. 怎么修复的:纯元数据对齐——master 的 package.json/package-lock.json 版本字段提到已发布的 0.1.192,不引入任何代码变更(先例 aeac5a8)。
  5. 是否有回归问题:无。diff 只有 3 行版本字符串,不触碰任何行为路径;高危模式(语义漂移/阈值/输出格式)逐项不适用。
  6. 是否破坏缓存:不涉及。
  7. 是否改了设计方向:不涉及。
  8. 是否引入了新的配置:不涉及。

收工判定:完成,可收工。owner 可以重新 dispatch Release (one-click) target 0.1.193。附带说明:master 上 kernel 现已走到 0.0.119(issue 写作时是 0.0.116,#2755 fold-summary head-stability fix 在内),0.1.193 将携带当前 master 的全部累积变更。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants