Skip to content

release v0.1.165 - #1556

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-28_release-v0.1.165
Sep 28, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-28_release-v0.1.165

Conversation

@github-actions

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

@github-actions

Copy link
Copy Markdown
Contributor Author

📦 Built Package Artifact

Branch: 2026-09-28_release-v0.1.165 (36522e2)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.1495-pr.1556.0a057c7-a2

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-pr1556.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Release PR review — v0.1.165 (version-range regression audit, policy ②b)

Reviewed the release PR itself AND the full window since v0.1.164 (tag..HEAD, 8 commits: 3 fixes + kernel pin + 2 test commits + 3 merges).

Release PR shape — clean

  • Branch 2026-09-28_release-v0.1.165, single commit 36522e24 release v0.1.165, based on current master tip 13a00139 (merge-base == master head, zero drift).
  • Diff is EXACTLY version 0.1.164 → 0.1.165 in package.json + package-lock.json (2 files, 3 insertions / 3 deletions). No content bundled into the release commit.
  • Drift guard holds: master's version == npm latest == 0.1.164; 0.1.165 is not yet published.
  • Cross-repo ordering respected: acp-kernel@0.0.98 is live on npm (verified npm view acp-kernel version).
  • CI on head 36522e24: all 13 checks green — typecheck-equivalent unit tests (ubuntu 22/24, windows 22/24), e2e (real codex vs deterministic fake upstream), hermetic registry e2e, all four client lanes (pi/opencode/dsh/codex MCP overlay), build-artifact, version-guard.

Window audit v0.1.164 → HEAD (per-change verdicts)

  1. fix: keep in-place summary in post-fold re-request view (fix: keep in-place summary in post-fold re-request view (Responses-wire cache collapse) #1551) — src/server.ts (~L5825, forward()/refreshFolded path). Old code mixed ephemeral acp_loop_* tool pairs into the message list before stripKernelSummaries judged carrier presence, so in proxy mode the proxy's own ephemeral compress call made it drop the in-place acp_summary for exactly one request (round-2), collapsing the upstream longest-prefix match to the stable head (observed production floor ~16.5K cached tokens after every fold instead of ~95%). New code strips against inbound-derived messages only, then appends the ephemeral records. Intended behavior change (disclosed): proxy-mode round-2 now retains the in-place summary and shares bytes through the fold anchor with the next client turn. Plugin mode (compress call rides inbound history) is explicitly unchanged. Regression-pinned by new tests/responses-fold-cache-seam.test.ts (drives a codex-shaped Responses session through the real proxy; asserts summary present in round-2, byte-identical prefix through the anchor, append-stability during plain growth). ✓
  2. fix: align google wire system anchor with folded re-request view (test+fix: cache-friendly outbound matrix across four proxy-mode wires (#1548) #1554) — src/server.ts (~L3662, prepareGoogle). The Google wire's injected system section skipped the triple-wrap (withConversationIdNote(withMarkerIntegrityNote(withSummaryBudgetNote(...)), ensureCanonicalId(session))) used by every other wire (anthropic/responses/openai) and by the folded re-request view itself — so the prefix forked at every fold and cache hits collapsed. Now aligned. Intended behavior change (disclosed): Google-wire system anchor bytes change (the three notes are added); they are byte-stable constants, so normal turns and round-2 re-requests now share the anchor. ✓
  3. fix: pin acp-kernel 0.0.97 → 0.0.98 (fix: pin acp-kernel 0.0.98 (content salvage + one-string batch) #1552) — exact pin (no caret), npm-live verified. Wire-contract goldens regenerated with justification stated in the commit (pack text change, kernel test: fix pipePluginChatWithStrip call order after #466 signature swap #472); I inspected every golden diff — bili.json / kernel.json / manifest-default.json / manifest-optin.json changes are description strings only (teaches "batch multiple ranges into ONE call", single-string form may hold all ranges), no schema structure changes. tests/compress-prompt-pack.test.ts expectations updated consistently. Kernel-side: single-object content salvage (track: plugin-mode proxy-side emergency truncation (last-resort backstop, deferred from #467) #470/release v0.1.72 #471) + one-string batch teaching (test: fix pipePluginChatWithStrip call order after #466 signature swap #472); fixes lean模式批量压缩丢失 #1495. ✓
  4. test commits (test+fix: cache-friendly outbound matrix across four proxy-mode wires (#1548) #1554 ×2) — purely additive: new tests/cache-friendly-proxy.test.ts (proxy-mode cache-friendliness matrix for all four wires) plus anthropic swallow/back-to-back geometry assertions (superset replaces, partial coexists, 19-fold monotonic tails). No existing behavior touched. ✓

Conclusion

本版本引入回归:无。 Three intended behavior changes, all disclosed above (proxy-mode post-fold summary retention → cache floor 16.5K→95% after folds; Google-wire system anchor gains the three byte-stable notes; compress tool description text teaches one-call batching via kernel 0.0.98). Nothing else moved. Release commit is a clean isolated version bump on current master, drift guard passes, full CI gate green including e2e. 可合并 — merging this PR publishes v0.1.165 via the standard release.yml flow.

Merging is human-only per repo rules — please merge yourself: #1556


中文摘要:审核了 v0.1.165 发版 PR 及其版本区间(v0.1.164 以来全部 8 个提交)——diff 为干净的纯版本号提交、基于最新 master、跨仓依赖 acp-kernel 0.0.98 已确认发布、CI 全绿(含 e2e);区间内 3 个行为变更均为有意且已披露(fold 后 proxy 模式保留 in-place summary、google 线 system 锚点对齐四线统一包裹、compress 工具描述随内核更新教 batch),未发现无意回归,可以合并。

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