Skip to content

release v0.1.112 - #792

Merged
ranxianglei merged 2 commits into
masterfrom
2026-09-15_release-v0.1.112
Sep 15, 2026
Merged

ranxianglei merged 2 commits into
masterfrom
2026-09-15_release-v0.1.112

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Release v0.1.112 — carries acp-kernel 0.0.70.

Two isolated commits on top of master:

  1. deps: bump acp-kernel 0.0.69 → 0.0.70 (+ lockfile) — the kernel release that shipped the wire image-preservation fixes (acp-kernel PR [bug] tag-echo 过滤器对截断的标签碎片剥离不完整,导致模型输出残留垃圾片段、整条消息被剥空 #294 / issue claude 登录版本上下文涨,压缩后泄露 #292).
  2. release v0.1.112 — version bump only (package.json + lockfile).

Why the kernel bump ships here

acp-kernel 0.0.70 is now live on npm (published after acp-kernel PR #294 merged), so billion-context can safely pin it. This is the "kernel first, then this version" sequencing requested in #772.

Changes since v0.1.111

Pre-flight (local, same checks as CI) — run against acp-kernel 0.0.70

  • npm run typecheck — pass
  • npm test — 1587 tests, 1585 pass / 0 fail / 2 skipped
  • npm run build — success (dist/index.js ~2.84 MB, acp-kernel 0.0.70 inlined)

Merging triggers .github/workflows/release.yml: CI runs npm ci + typecheck + test + build, then npm publish --tag latest, creates git tag v0.1.112, and creates the GitHub Release. No manual publish.

@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-15_release-v0.1.112 (2c17503)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-792

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

Option B — Download artifact

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

This comment is automatically updated on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Release PR verified independently against the branch 2026-09-15_release-v0.1.112 (tip 2c17503). All good:

Structure (per AGENTS.md release rules)

  • Branch name 2026-09-15_release-v0.1.112 matches the *_release-v* trigger pattern; base is master.
  • Exactly two isolated commits, no content bundled:
    • 7fb282f deps: — only acp-kernel 0.0.69 → 0.0.70 (package.json + lockfile), pinned exactly ("0.0.70", no caret).
    • 2c17503 release v0.1.112 — version bump only (package.json + lockfile), message matches the CI trigger convention.
  • Full diff vs master: 2 files, 8 lines (package.json, package-lock.json). Clean — no unrelated or whitespace changes.
  • Branch already contains the current master tip (bc1b2c4), so the merge will be conflict-free.

Cross-repo sequencing (kernel first)

  • npm view acp-kernel version → 0.0.70 (live on npm); npm ci on the branch installs exactly 0.0.70, which is what tsup inlines into dist/index.js. ✅
  • npm view billion-context version → still 0.1.111, i.e. nothing published yet; publishing will happen from CI on merge.

Local pre-flight on the release branch (same checks as CI)

  • npm run typecheck — pass
  • npm test — 1587 tests: 1585 pass / 0 fail / 2 skipped (matches your report)
  • npm run build — success, dist/index.js ≈ 2.84 MB with acp-kernel 0.0.70 inlined

One transparency note: I did not re-run the codex E2E suite here (it needs a live local Responses upstream to point at). This PR is a pure dependency-pin + version commit with no src/ changes, and the image-preservation fixes were validated in the acp-kernel release itself (#294/#292), so that's consistent with how prior dep-bump releases have shipped.

Duplicate screen: no other open issue/PR covers the v0.1.112 release — this PR is the single item.

⚠️ Per project rules I cannot merge PRs — please merge yourself: #792
After merge, CI will run npm ci + typecheck + test + build, publish billion-context@0.1.112 to npm (--tag latest), and create tag v0.1.112 + GitHub Release. Verify with npm view billion-context version.

中文摘要:独立复核了本发布 PR——diff 干净、两个提交严格隔离(依赖升级 / 版本号各一个)、kernel 精确锁定 0.0.70 且已先行发布到 npm、本地 typecheck/test/build 全过,可以合并(合并操作需人工执行)。

@ranxianglei
ranxianglei merged commit 2958c50 into master Sep 15, 2026
7 checks passed
@ranxianglei
ranxianglei deleted the 2026-09-15_release-v0.1.112 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