Repository navigation
release v0.1.186 - #2249
release v0.1.186#2249
Conversation
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.2346-pr.2249.797547eThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2249.tgz
npm install -g packageInstall instructions are refreshed on each push. |
[bot] 🏷 ## Release v0.1.186 版本区间回归审计(v0.1.185 → v0.1.186) 按发版本类 PR 规则,审查窗口从本 PR 的两行版本 diff 扩到 v0.1.185..master 全部变更:109 commits / 105 files / +13312 −614,作为一个整体综合审阅(含跨分支交互),非逐分支拼接。 PR 本体形状:release 分支 = master tip + 恰好一个 结构化七问
重大行为变更清单(旧值 → 新值 + 原因)
既有行为保全确认(抽样)
判定可合。 回归 0 处;15 项行为变更全部有意、披露、文档化;CI 全绿于该 commit;kernel 版本纪律成立;测试有牙。 |
v0.1.186 发布审查结论(v0.1.185 → b845822,106 文件 +13329/−617)审查方式:4 个分域(auto-update/发布、dsh/launcher、web/server/resign/kernel、pi-subagents/codex/win-cmd/side-lane)+ 本地验证(13 个关键测试套件全绿:launcher 275、launcher-sqlite-overlay 30、update 系列 27、dsh-compaction-guard 11、fold-reconcile 25、pi-subagent 10、issue2187 系列 6; ✅ 结论:可合并,无阻塞项关键行为变更均验证正确:#1234 opencode CACHE 副本豁免(实跑 MAJOR(跟进级,不阻塞,已开 issue)
发布前顺手修(一行级,不阻塞)
MINOR(已开 issue)
|
[bot] 🏷 结论收敛:两轮独立审查一致——可合并、无阻塞项。我的全窗口审计(v0.1.185..master,105 文件逐一过,CI 在 release commit c86eb5c 上 9 绿)同样判定可合、回归 0。 对你列出的发现做了代码级抽查(origin/master),结果:
跟进项 #2252–#2257 的分域合理(一个故障域一个 issue),本 PR 侧我这边没有遗留动作。等待人工合并:#2249 一点协调事项:#2090 若按 #1870 定为 severe,release-notes 条目可以作为独立 commit 加进本 release 分支(§5 允许,合并前落地即可);你确认后我立即推,否则随下个 release PR 走。 |
…ernel-review entry C2 of #2260 (v0.1.186 review): three kernel commits (146c75a/2a324f5/057d3a6) bumped kernel/package.json without regenerating the lock, leaving packages["kernel"] at 0.0.103; a sibling-checkout worktree install leaked an extraneous packages["../kernel-review"] entry (acp-kernel 0.0.42) present since v0.1.185. Regenerated via npm install --package-lock-only plus surgical removal of the unreferenced entry; verified stable (second run no-ops).
C1 of #2260 (v0.1.186 review): the middle segment of the [resign] startup banner was a double-quoted string, so http://${displayHost}:${actualPort}/__bili/ printed literally while its two neighbors were template literals.
…load (#2090 upgrade impact)
…config-load warning (en+zh)
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.185