Skip to content

[PR] release v0.1.212 - #5543

Merged
ranxianglei merged 2 commits into
masterfrom
2026-11-02_release-v0.1.212
Nov 2, 2026
Merged

ranxianglei merged 2 commits into
masterfrom
2026-11-02_release-v0.1.212

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

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

@ranxianglei ranxianglei changed the title release v0.1.212 [PR] release v0.1.212 Nov 2, 2026
@github-actions

github-actions Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor Author

📦 Built Package Artifact

Branch: 2026-11-02_release-v0.1.212 (7f9da94)

Latest build — install this exact version

npm install -g billion-context@0.0.7891-pr.5543.5510e45

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Recent builds (commit → version)

commit version build
7f9da94 billion-context@0.0.7891-pr.5543.5510e45 build
56d7bac billion-context@0.0.7886-pr.5543.e084477-a2 build

Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr5543.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

查重:不重复。v0.1.212 唯一有效发版分支 = 2026-11-02_release-v0.1.212(父提交 = 当前 origin/master 7f6ad2237,只多一个干净的 release v0.1.212 bump 提交)。另两个 2026-11-01_release-v0.1.212* 是过期/分叉的陈旧切点,已被取代,不在本 PR 树内。

一句话结论:可合。 本版本引入回归:0 处。我把 v0.1.211→master 整窗(60 commits / 88 files / +6294 −157)按高危域逐段读完,不是只看那两行版本号 diff;每个能改到默认用户行为的改动我都核了门控,全部是「默认关 / 灰度 / 更保守的加固 / 已披露的 owner 决策」之一。


高危域逐项点名核查(②b)

高危域 结果
自动更新/自更新 (src/update.ts) 未触碰 ✅
dsh 相关 dsh-native.ts 只加了 watermark 每槽 id 捕获(pfSlotIdsOf,? 占位不毒害邻居),纯增量;无 dsh 行为变化 ✅
版本钉死 / lockfile kernel 0.0.177→0.0.178 在 package.json + 两个 lockfile 三处一致;根 lockfile 记 acp-kernel 为 file: link(resolved:"kernel",link:true)正确;tests/golden/wire-contract/kernel.json 未变(默认配置字节级不变,ledger 未缩)✅
systemd / env 模板 本窗无此类文件改动 ✅
网络 / proxy 路径 watermark fastpath 任何校验 miss 都字节级回退 legacy;relay 只 merge x-bili-pf-* 命名空间头(不与上游头撞名);pf-channel.pfRequestHeaders 无状态时返回 {}(no-op)✅
CI / 发版门禁 正常发版的 drift guard + 重复发布保护保留不动;raw_publish 是手动勾选的应急通道,带 loud audit log,普通发版不受影响 ✅

行为变更清单(旧值→新值 + 原因)

  1. compress.compressAtFoldPoint / …ClearThinking:新增,默认 false。注意:changes-since 里同时出现「promote to default-on」和「keep opt-in (default off)」两条——后者(aeeb430f7)revert 掉了前者,净状态 = 默认关(opt-in via env / config / web 开关)。默认用户零变化;关闭时 relay out = outBase 原样,内核节点 fast-path 到同一数组引用。
  2. pluginFullResendWatermark:新增,5% 灰度(owner ruling 2026-11-02:先小队列,配 web 开关 + 一次性 intro notice)。此前该特性不存在。命中才省重算,miss 字节级走 legacy;可用 rollout.features.* / BILI_ROLLOUT_PLUGIN_FULL_RESEND_WATERMARK 覆盖。
  3. CI master push 臂:移除→ 由 :03/:33 schedule cron 充当 master 常驻校验(feat!: remove image pre-compression and the image_full tool (#3266) #3295/[PR] drop master from the CI push arm | ci: merge 后不再重跑 master 的 CORE 矩阵——那套结果没有任何消费者 #5426,owner 决策 2026-11-01:post-merge 重跑零消费者)。janitor 的 master 豁免同步扩到 schedule 跑。这是运维方向调整,PR 侧 blocking + release 各自 push 臂仍在。
  4. raw_publish 应急通道细化((ai: anthropic/claude-opus-4-6) The one-click release emergency switch skip_ci_gate does not take effect when the fall | (ai: anthropic/claude-opus-4-6) 一键发版紧急开关 skip_ci_gate 走 fallback 发版 PR 路径时不生效:勾了仍会派发全套 CI 并最多等 60 分钟全绿 #5430):deps 下载由 npm ci→npm install --no-audit --no-fund;连续两次应急发布时 master/npm 版本偏差不再阻断(改记 warning);bump 落成一个 commit 再打 tag/推 sync 分支(修掉「tag 指向旧版本树 + sync 分支空 diff 422」两个回归)。owner 决策 2026-11-01。
  5. 新配置面:2 字段 + 2 env(BILI_COMPRESS_AT_FOLD_POINT / …_CLEAR_THINKING),已入 CONFIGURATION.md en+zh,默认 false。

回归审查(逐项过高危模式)

  • 语义漂移:fold-point 默认关 ⇒ 默认布局字节级不变(已核 knobs.ts 默认 false + kernel golden 未变)。
  • fail-fast 变吞错:无。#5506 persist 折叠门反而更严——只有磁盘上证明落了这批 metadata 字节才折叠,分歧/无证明一律 fail-closed 保持驻留(只会推迟折叠,不会丢数据)。
  • wire 保真(kernel authorization request: heal must enforce the FOLLOW side of Anthropic's mid-conversation system position rule (#5432) #5438):mid-conversation system 规则补上 follow 侧(必须「跟随 user / 以 server tool_result 收尾的 assistant」且「前置于 assistant 或数组尾」)。这是对真实 Anthropic 约束的收紧/自愈,把原本会 400 杀会话的位置合法化降级为 user;严格后端更安全,lenient relay 上降级也安全(user 角色普适接受)。directive-only system 永不 heal、数组首 system 不受影响。双向模式都过。
  • turn-integrity(Context compression leak — rose to 350k | 上下文压缩泄露 涨到 35w #5531):新增可选 invisibleIds 参数,被块覆盖的 call 不再误判为 kept-visible,修掉「stranded reasoning 单调堆积直到无可折」。参数可选,不传即 legacy 行为。
  • 缓存策略:不失效。golden pin 未动;fastpath miss 走 legacy;fold-point 关时不 relocate。

测试有效性

窗口新增/改动 23 个测试文件,每个主要变更都有回归钉:issue5432-follow-side-heal、issue5531-stranded-reasoning-residue、issue4457-sidecar-system-folds、relocate-compress、compress-at-fold-point、fastpath/fastpath-scanner/issue5403-watermark-fastpath/wm-fastpath-intro-notice、persist-metadata-fold-gate、pf-channel、native-intercept、omp-msgids、lane-decisions-matrix、wire-contract/wire-exit-matrix、blog 管线三连等。断言有牙、覆盖正反(含 fastpath 的 hit/miss 双路)。

Caveats(诚实声明,均非阻断)

  • CI 实时绿我没读到:镜像缓存此刻空(套件运行中约 60s 一刷),GitHub API 从我这侧 egress 超时。我的可合判定基于 ②b 要求的整窗 diff 逐段通读,独立于 CI;权威全量信号仍是推上去后远程 CI test lanes + 三个 publish workflow 的 manifest --check。建议合并前确认这些 lane 绿(若 master 在合并前又动了,release 自带 drift guard 会中止而非静默发旧树)。
  • 小观察:① raw_publish 用 npm install(会跑依赖 lifecycle 脚本)而非 npm ci —— 对 owner 门禁的应急通道可接受,但记录在案;② 窗口内两条已合并的历史 commit message 措辞粗俗(「手动取消傻逼ai限制」「恢复老的ci release manal」),净效果合理,纯卫生问题,不影响本次发版;③ persist.metaFingerprint() 对不可序列化视图用 Math.random() 哨兵 → 该异常会话永不折叠驻留 metadata(fail-closed,安全,最坏只是内存回收略欠优,不丢数据)。

结构化八问

  1. 是什么问题:v0.1.212 的发版 PR(一键发版被分支保护挡住,回退成 PR)。审的是 v0.1.211→master 整窗,不是两行版本号。
  2. 什么原因导致的:N/A(非 bug,是发版);窗口内变更来自 [Feature][experimental] After compression, relocate the compress call pair to its own fold point (weak-attention models | [Feature][experimental] After compression, relocate the compress call pair to its own fold point (weak-attention models | [Feature… #5470/[Bug][dsh] 20k-message / 81 MiB-inbound session: host aborted 6× in 2 h — the #3050 resident-AST OOM is not bounded by sessions.hardMaxBytes (Windows, 0.1.210) #5403/[Bug][dsh] Plugin lane performs a full re-parse and resends the entire body every round (81 MiB → hundreds of MB AST), w | [Bug][dsh] plugin 车道每轮全量解析重发 body(81 MiB→数百 MB AST)是 #5403 OOM 的生产者:用水位线断言替换逐条复核,服务端只解析新增尾段 #5418/kernel authorization request: heal must enforce the FOLLOW side of Anthropic's mid-conversation system position rule (#5432) #5438/Context compression leak — rose to 350k | 上下文压缩泄露 涨到 35w #5531/Scheduled full test failed: ee0dcc7c | 定时全量测试失败: ee0dcc7c #5506/feat!: remove image pre-compression and the image_full tool (#3266) #3295/(ai: anthropic/claude-opus-4-6) The one-click release emergency switch skip_ci_gate does not take effect when the fall | (ai: anthropic/claude-opus-4-6) 一键发版紧急开关 skip_ci_gate 走 fallback 发版 PR 路径时不生效:勾了仍会派发全套 CI 并最多等 60 分钟全绿 #5430 等各自已合并的 PR。
  3. 影响范围与严重程度:默认用户面无行为变化(fold-point 默认关、watermark 仅 5% 灰度、其余更保守)。5% 灰度队列拿实验性 fastpath,miss 字节级回退 legacy。
  4. 怎么修复的:发版 = 干净的 master + 单一 bump(package.json + 4 插件 manifest 同步);内容窗每个高危改动逐段读并判 fail-safe。
  5. 是否有回归问题:0 处(高危模式逐项过完,见上)。
  6. 是否破坏缓存:不破坏(golden pin 未动、fastpath miss 走 legacy、fold-point 关时不 relocate)。
  7. 是否改了设计方向:无架构转向;新增均为可关的实验性能力。CI 由「master push 触发」转「schedule cron 常驻校验」是有意的运维调整(owner 拍板),非代码架构转向。
  8. 是否引入了新的配置:是——compress.compressAtFoldPoint(+env)、compress.compressAtFoldPointClearThinking(+env),默认 false,已文档化 en+zh;另有 rollout 特性 pluginFullResendWatermark(默认 5%)。

判定:可合。 无回归;所有行为变更要么默认关/灰度、要么是更保守的加固、要么是已披露的 owner 决策。请人工合并(我不能也不应代合):https://github.com/ranxianglei/billion-context/pull/(release-v0.1.212 分支 2026-11-02_release-v0.1.212)。合并前看一眼 CI lane 绿即可。

@ranxianglei
ranxianglei merged commit daa082e into master Nov 2, 2026
36 checks passed
ranxianglei pushed a commit that referenced this pull request Nov 2, 2026
The test file and code comments referenced the e-work mirror number
(5543), which on GitHub is the closed v0.1.212 release PR. The actual
issue is #5542 (generation reset invisible / swallowed execution tails)
— the same thread the commit message already closes. Rename the test
file and fix all in-code references so grep/Closes stay consistent.
ranxianglei pushed a commit that referenced this pull request Nov 2, 2026
The test file and code comments referenced the e-work mirror number
(5543), which on GitHub is the closed v0.1.212 release PR. The actual
issue is #5542 (generation reset invisible / swallowed execution tails)
— the same thread the commit message already closes. Rename the test
file and fix all in-code references so grep/Closes stay consistent.
ranxianglei pushed a commit that referenced this pull request Nov 15, 2026
The test file and code comments referenced the e-work mirror number
(5543), which on GitHub is the closed v0.1.212 release PR. The actual
issue is #5542 (generation reset invisible / swallowed execution tails)
— the same thread the commit message already closes. Rename the test
file and fix all in-code references so grep/Closes stay consistent.
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