Skip to content

release v0.1.196 - #2910

Closed
ranxianglei wants to merge 1 commit into
masterfrom
2026-10-12_release-v0.1.196
Closed

ranxianglei wants to merge 1 commit into
masterfrom
2026-10-12_release-v0.1.196

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Release v0.1.196 — version bump only (package.json + package-lock.json root fields, commit release v0.1.196).

Why now: ships the pi /new delegate fix (#2875, PR #2876) that npm latest (v0.1.195, cut from the bugfix-release/v0.1.195-dsh-compaction-422 carve-out before that merge) does not contain. Duplicate field report: #2906. After publish, pi users should update and restart pi; acp_delegate* / /acf-fleet must then survive /new.

No release-notes entry (ordinary release, not severe — #1870 opt-in).

Changes since v0.1.195

User-facing:

Tests:

CI/docs:

@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-12_release-v0.1.196 (674b6f1)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.3231-pr.2910.bd35591

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-pr2910.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

🏷 Release v0.1.196 — 版本区间回归审计完成(v0.1.195 tag..master,63 files,+3726/-192,全窗分批通读)

结构化八问:

  1. 是什么问题:这不是 bug 修复 PR,是版本发布——v0.1.195 从 bugfix-release carve-out 分支切出时漏掉了 pi /new delegate 修复(pi: acp_delegate tools and delegate prompt missing after /new or session switch (process-global "embedded" flag never reset) #2875),npm latest 至今没有它,pi 用户 /new 后 acp_delegate* 消失(现场报告 acf delegates lost on pi /new #2906)。本 PR 把 master 当前状态发成 v0.1.196。
  2. 什么原因导致的(窗口内头号修复的根因):pi-subagents 的 embedded 声明是进程全局的——第一个 session 的 markEmbedded() 把 Symbol.for("acp-delegate.embedded") 置真后永不释放,之后每次 runtime 重建(/new/reload/resume/fork)wirePiSubagents 在工厂级 if (embeddedClaimed()) return 处提前返回,delegate 工具/prompt/widget 静默丢失。修法:session_shutdown 时释放声明。我核对了该 symbol 的全部读写点(pi-subagents/src/index.ts:38-56 + src/agent/pi-subagents.ts),无其他消费者;跨扩展去重语义不受影响(shutdown 先于重建触发)。
  3. 影响范围与严重程度:发布覆盖全部 bili 用户;头号修复影响「pi + acp_delegate + 会话切换」用户,此前是完全不可用(工具静默消失),非体验瑕疵。其余为诊断/日志/归因增强,无外部行为面变化。
  4. 怎么修复的:见上——声明生命周期对齐 runtime 生命周期(claim 于工厂、release 于 shutdown),而非在读取侧加绕过。
  5. 是否有回归问题:本版本引入回归:0 处。高危域逐项点名核查:
  6. 是否破坏缓存:否。[Bug] Responses self-heal 切换投影规则后,提示词指纹变化被误归因为宿主改写 #2867 是归因层变更不是缓存层变更:前缀缓存本身的行为一个字节没动;变化的是 ledger 把「self-heal degrade-to-proxy 导致的转发 system 投影翻转」从 prompt 桶改记入新 projection 桶(canonical incoming 指纹稳定才判投影,任一侧未知回退旧的 host-side 读法,不伪造声明;旧持久化 ledger 加载时补零迁移安全)。
  7. 是否改了设计方向:无。全部变更落在既有机制内(ledger 归因分区扩展一位、日志降噪身份去重、诊断字段透传)。
  8. 是否引入了新的配置:无。CONFIGURATION.md en/zh 各 +5 行只是描述既有日志文件与新增的 5MB port-log 轮转;[diagnosis] 默认 direct 跳过可用的环境/系统代理时,失败提示从不点名那个代理 —— connect-timeout 只有「不可达/黑洞」,用户只能自己挖 registry 和源码 #2809 复用既有 upstreamProxyMode/BILI_UPSTREAM_PROXY_MODE,未发明新 knob。host-plugin 豁免状态写 state 目录运行时状态文件(与 instances.json 同级),不是 config surface。

重大行为变更清单(旧值→新值+原因,均为有意变更):

测试有效性抽查:每个行为变更都有对应新套件(cache-ledger-projection-switch 268 行、issue2752 479、issue2861 234、issue2879 208、responses-mode-switch-fingerprint 291、skipped-proxy-hint 227、logger-stderr-mute、port-log-rotation、hermes-native 双解析器分支含「两者皆缺」场景);storage-render golden ×4 按既有再生流程更新(伴随 ledger 行格式)。断言针对行为而非实现细节,回归时可抓。

CI:head 674b6f1 上全绿——双 CI leg + e2e(codex real/fake/persona/opencode/dsh/pi/ws)+ local-registry + image 共 13 个 run 全部 success。

一处非阻塞观察(§7.2 stale-base):PR head 基于 master 前一个提交,落后 #2898(issue2752 测试注册进 LIVE_FILES tripwire)一个 commit。已核实双方触碰文件不相交(package.json/lockfile vs scripts/run-ci-tests.mjs),合并无冲突,发布树 = 当前 master + 版本 bump,不影响本次发布;后续 release PR 建议切分支前先同步 master。

判定:可合。 合并后 npm latest 将包含 pi /new delegate 修复,pi 用户需更新并重启宿主生效。

@ranxianglei

Copy link
Copy Markdown
Owner Author

这个是从哪里触发的

ranxianglei added a commit that referenced this pull request Oct 12, 2026
…proval

docs: releases are owner-approved — agents propose, never cut version branches (#2910)
YunzhouLi-hub pushed a commit to YunzhouLi-hub/billion-context that referenced this pull request Oct 13, 2026
@github-actions github-actions Bot mentioned this pull request Oct 13, 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