Repository navigation
release v0.1.193 - #2767
release v0.1.193#2767
Conversation
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.3115-pr.2767.c9b8009This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2767.tgz
npm install -g packageInstall instructions are refreshed on each push. |
[bot] 🏷 收到 release v0.1.193 PR(来自 one-click workflow 的 auto-fallback)。已确认:release commit |
[bot] 🏷 Release v0.1.193 版本区间回归审计完成(v0.1.191..master,229 commits / 242 files) 审计覆盖:release commit 本身(package.json 0.1.192→0.1.193 + lockfile 4 行,纯版本号变更,干净);高危域逐行精读—— 本版本引入回归:未发现。 逐项既有行为结论:
重大行为变更清单(有意变更,旧值→新值):
新配置/依赖:
CI 状态:38 个 check runs — 31 success / 5 skipped / 0 failed;仅剩 2 个 windows-latest test 腿 in_progress(其余全绿)。且本窗口给 release 流程新增了「发布 sha 全量 CI 门禁」,合并后 CI 会在 publish 前再全量把关一次。 八问:
判定:可合。 等最后两个 Windows test 腿跑完即可(预计无风险;即便有异常,新的发布前全量 CI 门禁也会在 publish 前拦下)。合并请人工执行:#2767 |
[bot] 🏷 CI 收尾确认:38 个 check runs 全部完成 — 33 success / 5 skipped / 0 failed,最后两个 windows-latest test 腿也已转绿。审计结论不变:本版本引入回归:无,可合。请人工合并:https://github.com/ranxianglei/billion-context/pull/2767(合并后 release.yml 会按新门禁在 publish sha 再跑全量 CI,然后自动发布 v0.1.193)。 |
|
递补了几个进来 注意下 比如 #2763 可以自己扫描下 |
[bot] 🏷 递补提交扫描完成(增量窗口
增量行为变更清单(旧→新):① 空轮重试触发面扩大——纯空白/仅 reasoning 终轮现在会重试一次(旧:可见字节 >0 即抑制重试);② durable 身份不再接受 assistant 角色消息为 carrier;③ cache ledger 面板事件计数从「每维度各记一次」改为「单一主因记一次」(展示层,token 桶不变);④ agentless dsh compaction 调用在 raw URL 上也会被拦截进 passthrough lane 裁决(旧:直发漏网)。均为收紧/加固方向,无放宽。 分支状态:release 分支已再次同步到 CI(最终 head 结论:递补增量无回归,与首审结论一致——可合(待主 CI gate 转绿)。合并仍由人执行。 |
[bot] 🏷 CI 收尾确认(最终 head 结论不变:递补增量无回归,可合。合并由人执行:#2767 |
… carve-out entry that never merged back to master
…regressions) #2807 made the anonymous/identified identity chains hash the wire-NEUTRAL projection. That exposed three regressions (all three failing legs on the v0.1.193 release PR #2767): 1. The neutral projection MERGES a run of consecutive same-role messages into one turn (required for cross-wire equality — the anthropic render joins the run). A client that APPENDS another assistant message after an assistant tail (agent harnesses replaying model replies, fork follow-ups) re-renders the stored tail turn, so its item hash changes and the exact ladder fails by ONE item → fresh pfa-* mint → the fold ledger and the usage anchor are orphaned (spurious fork-of-fork children in fork-adoption-wires, 58701-vs-5000 sizing in issue2033-anonymous-anchor). Fix: per-source-message tail FRAGMENTS (fragmentHash) are now carried on every NeutralTurn, persisted on the chain (ChainEntry.tailFrags, snapshot round-trip included) and forwarded through note() from all resolve() paths. New rung 1.4 (append-continuation): a stored hv2 chain whose first K-1 items are byte-equal AND whose stored tail fragments are a strict PREFIX of the incoming turn-at-K-1 fragments is the same conversation extended in place → match instead of mint. 2. The v1 (pre-#2791 raw-wire) fallback rung could OUT-VOTE a matching hv2 chain by raw depth (raw counts MESSAGES, neutral counts TURNS — 16 vs 13 for the same history) and steal the request to a stale pre-upgrade duplicate session. Any user upgrading 0.1.192 → 0.1.193 hits this seam on their first post-upgrade request. Fix: within the ladder, hv2 candidates now take precedence over hv1; hv1 still resolves untouched when no neutral chain matches (legacy bridge). 3. Image placeholder text blocks were joined with "" into the neutral text, so the USER_IMAGE_PLACEHOLDER line filter could not strip them (issue2601 filter-branch replay). Placeholder blocks/parts are now dropped during neutral-text collection. Local: full targeted affinity sweep (27 suites) green; failing trio green.
…regressions) #2807 made the anonymous/identified identity chains hash the wire-NEUTRAL projection. That exposed three regressions (all three failing legs on the v0.1.193 release PR #2767): 1. The neutral projection MERGES a run of consecutive same-role messages into one turn (required for cross-wire equality — the anthropic render joins the run). A client that APPENDS another assistant message after an assistant tail (agent harnesses replaying model replies, fork follow-ups) re-renders the stored tail turn, so its item hash changes and the exact ladder fails by ONE item → fresh pfa-* mint → the fold ledger and the usage anchor are orphaned (spurious fork-of-fork children in fork-adoption-wires, 58701-vs-5000 sizing in issue2033-anonymous-anchor). Fix: per-source-message tail FRAGMENTS (fragmentHash) are now carried on every NeutralTurn, persisted on the chain (ChainEntry.tailFrags, snapshot round-trip included) and forwarded through note() from all resolve() paths. New rung 1.4 (append-continuation): a stored hv2 chain whose first K-1 items are byte-equal AND whose stored tail fragments are a strict PREFIX of the incoming turn-at-K-1 fragments is the same conversation extended in place → match instead of mint. 2. The v1 (pre-#2791 raw-wire) fallback rung could OUT-VOTE a matching hv2 chain by raw depth (raw counts MESSAGES, neutral counts TURNS — 16 vs 13 for the same history) and steal the request to a stale pre-upgrade duplicate session. Any user upgrading 0.1.192 → 0.1.193 hits this seam on their first post-upgrade request. Fix: within the ladder, hv2 candidates now take precedence over hv1; hv1 still resolves untouched when no neutral chain matches (legacy bridge). 3. Image placeholder text blocks were joined with "" into the neutral text, so the USER_IMAGE_PLACEHOLDER line filter could not strip them (issue2601 filter-branch replay). Placeholder blocks/parts are now dropped during neutral-text collection. Local: full targeted affinity sweep (27 suites) green; failing trio green.
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.191
compress.stripImages默认开启——否则带图消息不可压缩会形成只升不降的输入地板撑爆上下文 #2607): remove compress.stripImages — default media folding replaces itcompress.stripImages默认开启——否则带图消息不可压缩会形成只升不降的输入地板撑爆上下文 #2607): close the two e2e gaps — decompress round-trip after a default fold, google inlineData foldcompress.stripImages默认开启——否则带图消息不可压缩会形成只升不降的输入地板撑爆上下文 #2607)compress.stripImages默认开启——否则带图消息不可压缩会形成只升不降的输入地板撑爆上下文 #2607)