Skip to content

release v0.1.163 - #1517

Merged
ranxianglei merged 3 commits into
masterfrom
2026-09-27_release-v0.1.163
Sep 27, 2026
Merged

ranxianglei merged 3 commits into
masterfrom
2026-09-27_release-v0.1.163

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

@ranxianglei

Copy link
Copy Markdown
Owner

又合并了两个issue进来注意

@github-actions

github-actions Bot commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor Author

📦 Built Package Artifact

Branch: 2026-09-27_release-v0.1.163 (0bff16a)

Option A — Install this exact build (recommended)

npm install -g billion-context@0.0.1458-pr.1517.d02c74d

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

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner

#1478 已经进入

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷

release v0.1.163 review (PR #1517) — audited against live master after the late merges you flagged.

Late merges handled correctly:

Release-trigger sanity: release.yml matches the merge commit's Merge pull request … /2026-09-27_release-v0.1.163 via its branch-name regex, so publishing still fires even though the release v0.1.163 commit now sits below the sync merge commits. Version guard passes (0.1.x line). Post-merge master carries 0.1.163 > npm latest 0.1.162 → publishes latest, tags v0.1.163, and the auto-generated Release notes (git log since last tag) will include all changes — including the three late ones (#1499, #1506, #1478).

Window audit v0.1.162..master (10 content commits, every diff reviewed):

本版本引入回归:无。

Behavior-change ledger (old → new):

  1. Emergency-shrink arming after no-usage failures ([Bug]Preflight compression uses raw-history estimate instead of compressed-payload size — 42–203s stall per request, saves ~1K tokens #1493 + rework): raw-body chars/4 → outbound payload estimate. Preflight keeps the billing-accurate estimate as its floor; the arm value is floored by the text char bound (max(text est, upper bound) + overhead + images). Net: image-heavy payloads arm lower (no more false preflights on fitting payloads), dense near-window text arms higher (keeps the arm emergency shrink on upstream failure to break relay-5xx deadlock #604 relay rescue deep enough). Also: benign "payload fits" preflight log warn→info.
  2. Unparseable compress args (proxy 工具参数 JSON 解析失败被降级为空对象执行,原始字符串被丢弃、lenient 容错层被绕过 #1502): degraded to {} (empty-call verdict) → routed to the kernel's lenient salvage ladder; unsalvageable strings get their own corruption receipt (length-only label, no payload echo). Non-compress proxy tools unchanged (still {}).
  3. Truncation continuation nudge (anthropic 线缺少 continuation-nudge 恢复路径:第二道截断闸门硬编码 openai-only #1470/feat: extend truncation continuation nudge to the anthropic wire (#1470) #1478): openai wire only → openai || anthropic. responses/google stay excluded (fix: acp-loop zero-side-effect truncation retry + well-formed anthropic error stream (#413) #440 single-created invariant); anthropic re-fetch hazards neutralized by the fix: gate truncation retry on visible output, not any forwarded byte; ride stream failures on protocol-native error frames (#1455) #1464 adapter.
  4. Compress receipts (compress failed may be caused by params #1494/lean模式批量压缩丢失 #1495): parse-dropped entries, truncated-salvage loss, and apply-layer per-range errors are now named on the model-facing receipt — additive text on paths that previously read as clean success. Compression itself unchanged.
  5. Nameless tool calls ([policy] Nameless tool calls on verbatim-forwarding lanes: drop like the synthesis lane (#1484), or keep upstream bytes verbatim (#1039)? #1501): new once-per-response warn on verbatim lanes — observe-only, bytes forwarded untouched ([bug] 插件透传会剥掉工具调用参数里的 render tag(arguments 流挂了 tag-echo 过滤器) #1039 invariant preserved).
  6. acp-kernel pin 0.0.95 → 0.0.97: live on npm as latest; CI installed and tested it green.
  7. Log-only (Native compaction log reports undefined live ref count #1513): native-compaction boundary pruned count rendered undefined → real count. Pruning itself was always correct.

Non-behavioral: MESSAGE-IDENTITY docs (#1506), ccr resend-semantics test assertions, 2-line comment cleanup.

CI: prior head 1602ec61 fully green (CI + all e2e lanes + hermetic registry + build). Current head 0bff16a8: e2e / native lanes / codex / dsh / registry / build / version-guard already green; unit-test matrix still running, zero failures so far — I'll follow up here when it lands.

Everything checks out. Merge is human-only per repo rules: #1517

中文摘要:已审完 v0.1.162→v0.1.163 全窗口(含你提示的 #1499/#1506/#1478 三个后并入项),未发现回归;行为变更均为有意且已逐条列明,分支相对 master 只剩版本号改动,CI 全绿(测试矩阵收尾中),可以合并。

@ranxianglei

Copy link
Copy Markdown
Owner

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷

CI follow-up for head 0bff16a8: fully green. The last in-progress jobs have landed — unit-test matrix (ubuntu 22/24, windows 22/24) all success, alongside e2e / native lanes / codex overlay / hermetic registry / build-artifact / version-guard. Zero failures or cancellations on the final head.

Nothing outstanding from my side — #1517 is ready for a human merge; merging it triggers the standard release.yml publish (v0.1.163 → npm latest, tag + GitHub Release with notes covering all ten changes since v0.1.162).

中文摘要:最终提交 0bff16a 的 CI 已全部转绿(含收尾的测试矩阵),无失败项,PR 可合并。

@ranxianglei
ranxianglei merged commit 59d6f16 into master Sep 27, 2026
18 checks passed
@ranxianglei
ranxianglei deleted the 2026-09-27_release-v0.1.163 branch October 15, 2026 05:32
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