Repository navigation
release v0.1.183 - #2058
release v0.1.183#2058
Conversation
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.2101-pr.2058.0cf796e-a2This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2058.tgz
npm install -g packageInstall instructions are refreshed on each push. |
[bot] 🏷 Release PR review — v0.1.183 Verified the branch ( PR shape — clean. Exactly one commit CI — fully green. All 4 unit-test lanes (ubuntu/windows × node 22/24), version-guard, build-artifact, real-client e2e lanes (codex, opencode native, opencode V2 Responses WS, pi, dsh), hermetic registry e2e (ubuntu + windows — exercises the real self-update chain), real-image billing e2e, codex-overlay lane. Cross-repo ordering — ok. Window contains the acp-kernel pin bump 0.0.100 → 0.0.101 (from the #1960 redacted-thinking fix). Verified 0.0.101 is live on npm before judging this PR; CI Load-bearing areas deep-read (regression verdict: none broken):
Behavior-change ledger (old → new, all intentional, all in-window):
Caveat (flagged, not blocking): the updater changes (#1603/#1632/#2030 touch 结构化七问:
判定:可合。 请人工合并合并后 CI 自动发布。(另:updater 变更未走独立 NO-OP 验证发布一事已按上文披露,供记录。) |
PR #2058 合并 Diff 回归审查报告(v0.1.181 → pr2058)按「合并为一个大 diff 审查、重点看回归、必要时本地验证」完成。结论:未发现阻断性(blocking)回归,可以合并。 153 commits / 411 files(+15701/−1505)逐块过完,所有行为变化都能对应到有意的修复或策略决策。 一、自动更新子系统(重点)安装管线(备份→拷贝→校验→回滚)完全未动,改动全部在外围防护与提示策略,方向都是「响亮失败优于静默错装」:
二、其他集群(按风险从高到低)
三、本地验证
四、非阻断跟进对应问题已单独开 issue 跟踪:WS 背压硬失败、fork 快照每请求克隆/持久化体积、knobs+出站估计的每请求开销、#1977 可见性变化的文档说明。 |
[bot] 🏷 Cross-review reconciliation — two independent audits, same verdict I audited the same PR from the user-upgrade-delta angle ( 1. #1977 visibility change — you're right, my ledger missed it. Verified at commit level:
Your classification stands: this is the most regression-looking surface in the whole window, and it's deliberate with a documented escape hatch. 2. #1985 mitm port — your characterization is the accurate one. I read the hunk ( 3. Follow-up issues — all four verified filed and open: #2076 (WS backpressure hard-fail at 4. Your local validation closes the one caveat I raised. My only reservation was that the 结构化七问(交叉核对轮):
判定:可合。 两份独立审计(v0.1.182 增量视角 + v0.1.181 全窗口视角)、CI 全绿、本地基线对照验证齐备;四个跟进问题已立项跟踪。等待人工合并,CI 自动发布。 |
Auto-fallback from the one-click release workflow: direct push to master was blocked by branch protection. Merging this PR publishes via the standard release.yml flow.
Changes since v0.1.181
developer角色插入历史中段,严格单-system 后端 400「System message must be at the beginning」 #1999 residual)developer角色插入历史中段,严格单-system 后端 400「System message must be at the beginning」 #1999)protocolfield — path-scoped wire-protocol declaration #2019): correct non-shadowing wording to match actual resolution semanticsprotocolfield — path-scoped wire-protocol declaration #2019): web config save returns 400 for malformed providers.protocolprotocolfield — path-scoped wire-protocol declaration