Repository navigation
[PR] release v0.1.185 - #2109
ranxianglei wants to merge 1 commit into
Conversation
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.2154-pr.2109.3ec60eaThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2109.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Review 结论:可合 ✅(NO-OP 验证发布,窗口回归审计通过)按发版本类 PR 规范做了 v0.1.184 → v0.1.185 全窗口回归审计(5 个已合 PR 合并为一个整体审阅),并逐项验证了 issue 声明。 结构化七问
重大行为变更清单(均有意的 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 内验证协议执行: |
|
关闭:僵尸发版 PR。release v0.1.185 提交(patch 等价)已在 master,tag |
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) modifiessrc/update.tstemp-file mechanics (installViaTarballstaging/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 particularsrc/update.tsis 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)
fix: bili codex pins embedded mode via probed --no-daemon(+ win32 launcher test fakes)fix: stamp nativeCaller on host-native agent tool forwarding(+ hermes channel pin test)docs(configuration): Server Settings entries+fix(config): KNOWN_TOP_LEVEL_KEYS missed 4 consumed FileConfig fields+feat(knobs): migrate BILI_POST_RESPONSE_LINGER_MS to network.postResponseLingerMsfix: handoff role mislabelValidation protocol after merge (owner steps)
npm view billion-context version== 0.1.185.update: upgrading to 0.1.185… success).If the no-op upgrade fails anywhere: STOP, do not merge #2108, diagnose the upgrade path first.