Skip to content

[PR] release v0.1.185 - #2109

Closed
ranxianglei wants to merge 1 commit into
masterfrom
2026-10-04_release-v0.1.185
Closed

ranxianglei wants to merge 1 commit into
masterfrom
2026-10-04_release-v0.1.185

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

NO-OP validation release — required BEFORE merging PR #2108

Per AGENTS.md §5 ("Changing src/update.ts (the updater itself) requires a NO-OP validation release FIRST"): PR #2106-fix (#2108) modifies src/update.ts temp-file mechanics (installViaTarball staging/backup/tarball paths, syntaxCheckEntry). A broken updater bricks every future upgrade, so the existing upgrade path must first be proven healthy end-to-end by shipping a version whose updater code is byte-identical to the published one.

This PR changes ONLY version (0.1.184 → 0.1.185, package.json + package-lock.json, same shape as release commit 0bec76c). No product change anywhere — in particular src/update.ts is untouched, so installed 0.1.184 instances will run the OLD updater code to fetch and install 0.1.185.

Changes since v0.1.184 (already on master, carried by this build)

Validation protocol after merge (owner steps)

  1. Confirm npm view billion-context version == 0.1.185.
  2. Observe at least one real production instance auto-upgrade 0.1.184 → 0.1.185 successfully (log line update: upgrading to 0.1.185 … success).
  3. ONLY THEN merge PR fix: unique per-invocation update temp paths to end cross-process cacheDir races (#2106) #2108 and cut the next release (v0.1.186) carrying the updater fix.

If the no-op upgrade fails anywhere: STOP, do not merge #2108, diagnose the upgrade path first.

@github-actions

github-actions Bot commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-04_release-v0.1.185 (f968e0a)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.2154-pr.2109.3ec60ea

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-pr2109.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

Review 结论:可合 ✅(NO-OP 验证发布,窗口回归审计通过)

按发版本类 PR 规范做了 v0.1.184 → v0.1.185 全窗口回归审计(5 个已合 PR 合并为一个整体审阅),并逐项验证了 issue 声明。

结构化七问

  1. 是什么问题:不是缺陷——是流程要求。fix: unique per-invocation update temp paths to end cross-process cacheDir races (#2106) #2108 要改 src/update.ts 的临时文件机制,AGENTS.md §5 规定改 updater 前必须先发一个 updater 字节不变的 NO-OP 版本,证明现有升级链路端到端健康。
  2. 什么原因导致的:无根因。这是「broken updater bricks every future upgrade」风险的既定防线。
  3. 怎么修复的:纯版本号 bump(0.1.184 → 0.1.185)。已验证 git diff v0.1.184..pr-2109 -- src/update.ts = 0 行差异——装机 0.1.184 实例将用旧 updater 代码拉取安装 0.1.185,声明成立。
  4. 是否有回归问题:本版本引入回归:0 处。窗口内 5 个变更逐项过高危模式(fail-fast 变吞错 / 阈值时序漂移 / 输出格式变化 / 缓存重试策略):
  5. 是否破坏缓存:不涉及。无任何缓存/重试/去重策略变化;fix(cache-ledger): attribute tail-append misses to provider-side, not seam suspects (#2059) #2061 只改 miss 的诊断归属(seam→provider-side),不改缓存行为本身。
  6. 是否改了设计方向:不涉及。
  7. 是否引入了新的配置:是,一处——network.postResponseLingerMs(既有 env BILI_POST_RESPONSE_LINGER_MS 的文件层,默认 5000,env 仍优先;无需迁移,想用文件配置才设)。另有 4 个既有字段进入已知键表(消除误报警告,非新表面)。已在 CONFIGURATION.md en/zh 同步。

重大行为变更清单(均有意的 fix,旧值→新值)

两点备注

CI:head f968e0a 上 11/11 全绿(CI×2、e2e-native-dsh/pi/opencode、E2E real codex、e2e-fake-codex、e2e-local-registry、ci-image、Windows codex overlay、PR Build Artifact)。PR diff 相对 master 恰好只有 package.json + package-lock.json 三行版本变更。

合并后请按 issue 内验证协议执行:npm view billion-context version == 0.1.185 → 观察至少一个生产实例 0.1.184→0.1.185 自动升级成功(log update: upgrading to 0.1.185)→ 之后再合 #2108 并切 v0.1.186。若 no-op 升级任何环节失败:STOP,先诊断升级路径。

@ranxianglei

Copy link
Copy Markdown
Owner Author

关闭:僵尸发版 PR。release v0.1.185 提交(patch 等价)已在 master,tag v0.1.185 已存在,其后已发布 18 个版本(当前 v0.1.203)。发版使命早已完成。(孤儿 PR 扫描,证据链:讨论 #3916)

@ranxianglei ranxianglei changed the title release v0.1.185 [PR] release v0.1.185 Oct 21, 2026
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.

1 participant