Skip to content

chore: pin acp-kernel 0.0.91 - #1331

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-25_kernel-0.0.91
Sep 25, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-25_kernel-0.0.91

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Pin bump acp-kernel 0.0.90 → 0.0.91 (exact pin, lockfile refreshed).

What it picks up

Pre-flight (pinned 0.0.91)

  • typecheck ✅
  • tests: 2574 pass / 0 fail (e2e-gated skips as usual)
  • build ✅ (dist-import-annotations OK)

No bili-side code changes required — both compression lanes normalize ids before the kernel sees them; this keeps the pinned floor on the fixed kernel. After this lands, master is ready for the 0.1.150 release (refold wiring #1316, receipt enhancements #1298, pi dead-path fix #1319, overflow-refold retry #1328).

Picks up #422/#421: syncBlocks no longer crashes processTurn on
id-less host-shaped messages (0.0.90 regression from the #233
subid-coverage pass; every earlier release silently digested that
shape). No bili-side changes required — both lanes normalize ids on
their own paths; this keeps the pinned floor at the fixed kernel.
@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-25_kernel-0.0.91 (71bf3f2)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-1331

Each push to this PR publishes a new version under the pr-1331 npm tag.

Option B — Download artifact

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

Install instructions are refreshed on each push.

@ranxianglei
ranxianglei merged commit 108fb40 into master Sep 25, 2026
11 checks passed
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Review complete — mergeable. Verified independently, not just trusting the pre-flight claims:

① Direction (original issue): Confirmed the fix exists where claimed. Pulled both published tarballs and diffed them: acp-kernel 0.0.90 → 0.0.91 differs in exactly one place — syncBlocks gains the id guard (0.0.90 line 297 calls baseIdOf(message.id) unconditionally; 0.0.91 wraps it in if (typeof message.id === "string")). That is precisely the #422/#421 fix (id-less host-shaped messages no longer crash processTurn). npm confirms 0.0.91 is live (npm view acp-kernel version → 0.0.91) and master currently pins 0.0.90, so the bump direction is correct.

② Regression audit (version window 0.0.90→0.0.91): Full dist diff = that single hunk only; the two packages' package.json are identical apart from version. So the entire behavioral delta this PR ships is the crash fix — nothing else moved. Bili-side diff is package.json (1 line) + package-lock.json (the acp-kernel entry: version/resolved/integrity) — no code paths touched, so all existing behaviors (both compression lanes, wire fidelity, persistence format) are preserved by construction. Existing-behavior checklist: compression pipeline ✅ unchanged · session/persist format ✅ unchanged · wire shape ✅ unchanged · config schema ✅ unchanged.

③ Code & diff cleanliness: Exact pin, no caret (spec §2 decision #5 honored); lockfile refreshed with new integrity hash; 5 lines total, every line on-purpose. Branch sits directly on current master tip (60df397) — no stale-base risk.

④ CI: All 11 checks green on head 71bf3f2 (test ubuntu 22/24, windows 22/24, e2e + real-client lanes, hermetic registry e2e, version-guard, build-artifact); mergeable_state: clean.

⚠️ Behavior change flag (per deliverables rule 4): kernel 0.0.90 → 0.0.91 changes one past behavior: input containing id-less host-shaped messages previously threw a hard TypeError in processTurn; now those entries are skipped when building presentBases (restoring the silent-digest behavior of ≤0.0.90). Since both bili lanes normalize ids before the kernel sees them, this is a defensive floor — no observable change in normal operation; it only stops the crash for unnormalized consumers (pi-side tests, billion-context-pi#536). Intended, not drift.

No action needed from me — merge is human-only: #1331

一句话中文摘要:审核通过——kernel 0.0.91 相对 0.0.90 仅含 #422 的 syncBlocks 空 id 守卫这一处改动(已拉两个 tarball 逐行比对确认),bili 侧只动版本钉与 lockfile,CI 11 项全绿,无回归,可以合并。

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