Skip to content

release v0.1.195 - #2857

Merged
ranxianglei merged 3 commits into
masterfrom
bugfix-release/v0.1.195-dsh-compaction-422
Oct 12, 2026
Merged

ranxianglei merged 3 commits into
masterfrom
bugfix-release/v0.1.195-dsh-compaction-422

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Bugfix carve-out release — publishes ONLY this PR + version bump (#2851)

Cut from tag v0.1.194 (last released), containing exactly:

  1. e759b24a6 fix: refuse dsh native compaction with 422, not auth-class 403 (cherry-pick of fix: refuse dsh native compaction with 422, not auth-class 403 (#2843) #2844's fix commit 46f6e931b, author Mintapril preserved)
  2. 7c41abd29 release v0.1.195 (version bump only: package.json 0.1.194→0.1.195 + lockfile sync)

Deliberately excluded — unreleased master work after v0.1.194: #2834 (probe stderr silence), #2791 (responses/google affinity), #2832 (preflight deterministic empty), #2619 (draft-tail-compaction), #2828/#2824 (sketch image perf), #2829 (fetch-chain log channel). They stay on master for the next normal release (which must be ≥ 0.1.196).

On merge, the PR-gated release-bugfix.yml (#2853, merged today) checks out THIS pre-merge head tree and publishes v0.1.195 to npm latest — the artifact is exactly this branch, nothing else. All fail-closed guards run as usual (monotonic vs npm latest 0.1.194 ✓, not-already-live ✓, full pre-flight + full-CI gate at this sha).

No severe-behavior entry needed in release-notes (opt-in severity declarations only, #1870).

Closes #2851.

Mintapril and others added 2 commits October 12, 2026 11:09
dshCompactionRefusal() answered 403 on every lane. 401/403 is the credential-failure class (HTTP semantics; Anthropic pairs 403 with permission_error, while the anthropic-lane refusal paired it with invalid_request_error), so clients that classify by status read a local policy refusal as a credential failure and may disable the credential. 422 keeps the refusal a non-retryable client error (not 408/409/429/5xx) without the auth semantics; body shapes are unchanged.

Fixes #2843
@github-actions

github-actions Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: bugfix-release/v0.1.195-dsh-compaction-422 (f76ffe9)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.3175-pr.2857.d9e7911

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

[bot] 🏷 收到。这是发版本类 PR(bugfix carve-out,v0.1.194 → v0.1.195),按 owner policy 触发版本区间回归审计:正在拉取 PR head、核对 v0.1.194..head 全窗 diff、比对 #2844 原始 fix commit(46f6e931b)的 cherry-pick 保真度、确认排除项未混入、核查 release-bugfix.yml 门禁与 CI 状态。结论稍后按结构化八问回帖。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 版本区间回归审计完成(v0.1.194..head,12 文件逐段通读;高危域 dsh 相关全部逐行)。结论:审计项全过,但 CI 有一处红,先修再合。

结构化八问

  1. 是什么问题:bugfix carve-out 发布——只发 fix: refuse dsh native compaction with 422, not auth-class 403 (#2843) #2844 的 dsh native compaction 拒答状态码修复(403→422)+ 版本 bump,刻意排除 master 上 v0.1.194 之后的全部未发布工作。
  2. 什么原因导致的(被修缺陷的根因):dshCompactionRefusal() 对所有 lane 统一回 403;401/403 在 HTTP 语义里是 credential-failure class,按状态码分类的客户端会把"本地策略拒答"误读为凭据失效(可能禁用凭据),而 422 保持 non-retryable client error(非 408/409/429/5xx)且不带 auth 语义。
  3. 影响范围与严重程度:四协议 lane(openai/anthropic/responses/google)的 dsh compaction 拒答响应面;特定条件下有问题(客户端对 auth-class 4xx 采取行动时),无数据丢失、无不可用,body 形状不变。
  4. 怎么修复的:状态码改为 422,body 形状不动;新增回归测试断言所有 lane "既非 auth-class 也非 transient-class"(not 401/403、not 408/409/429/<500),把语义钉死。
  5. 是否回归问题:窗口内逐项核查——cherry-pick patch 与 fix: refuse dsh native compaction with 422, not auth-class 403 (#2843) #2844 原提交 46f6e931b 字节级一致(md5 相同),作者 MintApril 保留;分支 = tag + 恰好 2 commits,merge-base = v0.1.194 本身,零 master 泄漏,排除清单(Git stderr leaks into terminal on startup when package dir is not a git repo #2834/dsh anthropic-messages lane bypasses native-intercept fetch patch: anonymous pfa-* session, fold ledger orphaned, silent ~182s re-fold on cross-protocol switch #2791/[Bug] preflight 把确定性的 end_turn 空摘要判为「瞬时故障」:每个 span 烧尽重试预算、零 fold 落地,且诊断无法区分 thinking-only 与正文被中继吞掉(0.1.188→0.1.193 未修) #2832/fix: skip draft-tail retry when the request itself asks for the summary (#2612) #2619/fix: eliminate 0.1.193 long-session CPU regression — unused SimHash sketches + duplicate history conversions (#2824) #2828/[性能回归] 0.1.193 长会话本地耗时从 1.3s 升至 3.2s:无用 SimHash 计算与重复历史转换 #2824/fix(#2827): route native fetch-chain diagnostics to bili.log instead of console.* #2829)逐一确认不在祖先链上;release commit 只动 package.json+lockfile 的 version 行(符合 §4);高危域点名:自动更新路径未触碰 ✓ / lockfile 仅版本行 ✓ / 无 env/systemd 模板 ✓ / 消费方 sweep(src/server/handle.ts、src/conflict-watch.ts)确认无代码依赖旧 403 值 ✓。但 CI 红了一处:CI workflow 的 version-guard job 失败(runs 38198762957)——ci.yml 只放行 *_release-v* 分支,不识别 bugfix-release/* carve-out 前缀,是 feat: route bugfix carve-out releases through a PR like normal releases (#2851) #2853 改造通道时漏掉的 guard 兼容性。已立项 ci.yml version-guard 不识别 bugfix-release/* carve-out 分支:#2853 新通道下所有 carve-out 发布 PR 必红 #2858(含复现、根因、一行修法;注意不能反过来改 carve-out 分支名为 *_release-v*,那会让 release.yml 合并时二次发布)。其余 9 条 lane 全绿。
  6. 是否破坏缓存:不涉及——未触碰任何缓存/重试/增量游标/去重逻辑。
  7. 是否改了设计方向:不涉及——机制不变,仅状态码语义修正。
  8. 是否引入了新的配置:不涉及。

行为变更披露(旧值→新值):dsh compaction 本地拒答的 HTTP 状态 403 → 422(anthropic lane 与 generic lane 均变),body 形状不变;原因见第 2 问。PR 标题/正文已声明,符合披露要求。

判定:❌ 暂不可合。阻塞项唯一:version-guard 红。由于 release-bugfix.yml 的 Full-CI gate 是 fail-closed 的,现在合并不会误发布(会卡在 gate 上),但通道卡死;建议等 #2858 的 ci.yml 修复落 master 后 re-run 本 PR CI 转绿再合。发布物内容本身(tag + fix + bump,精确 carve-out)审计无误。

LoveDoLove pushed a commit to LoveDoLove-Forked-Projects/billion-context that referenced this pull request Oct 12, 2026
ranxianglei#2853 made the carve-out channel PR-gated with bugfix-release/* as the marker prefix, but ci.yml version-guard still only whitelisted *_release-v*. Every carve-out release PR (e.g. ranxianglei#2857) went red, and release-bugfix.yml's fail-closed full-CI gate then blocked the merge-time publish.
@ranxianglei

Copy link
Copy Markdown
Owner Author

现在可以合成了吗 确认只有一个 fix 对吗

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 直接回答:不,现在分支里不止一个 fix 了——我审计后分支被推进过,不能按原描述合。

事实(刚重新核对)

两条路,选一条我再放行

  1. **维持原 carve-out 意图(只发 dsh-422 fix)**→ 把分支恢复到我审计过的 7c41abd29(force-push PR 分支,非 master,合规;CI 会在修好的 guard 下重跑转绿)。你说一声我就执行,然后可合。
  2. 其实想全量发(即放弃 carve-out、当常规 release)→ 那这个通道/这个树都不对了:应从当前 master 头(3269d71cb)切 *_release-v* 分支走常规通道,artifact 与 master 完全一致;本 PR 关闭或改写说明。

我的建议是 路线 1:PR 正文的发布范围声明("publishes ONLY this PR + version bump")仍然成立的前提就是纯树,恢复一行命令的事。等你的决定。

@ranxianglei

Copy link
Copy Markdown
Owner Author

**维持原 carve-out 意图(只发 dsh-422 fix)**→ 把分支恢复到我审计过的 7c41abd(force-push PR 分支,非 master,合规;CI 会在修好的 guard 下重跑转绿)。你说一声我就执行,然后可合。

@ranxianglei

Copy link
Copy Markdown
Owner Author

我看风险不大 直接发了

@ranxianglei
ranxianglei merged commit 23186d5 into master Oct 12, 2026
28 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.306-master.23186d5 (rolling master tag).

npm install -g billion-context@0.0.306-master.23186d5  # this exact build
npm install -g billion-context@master  # always the newest merged build

npm view billion-context@master prints the current version at any time.

@ranxianglei ranxianglei mentioned this pull request Oct 12, 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.

bugfix通道也走pr而不是静默推分支

2 participants