Skip to content

release v0.1.113 - #795

Merged
ranxianglei merged 3 commits into
masterfrom
2026-09-15_release-v0.1.113
Sep 15, 2026
Merged

ranxianglei merged 3 commits into
masterfrom
2026-09-15_release-v0.1.113

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Release v0.1.113.

Changes since v0.1.112

Dependency bump

  • acp-kernel 0.0.70 → 0.0.71 (2f43f26) — blank reasoning_content round-trip fix (acp-kernel #295). Confirmed live on npm before this bump.

Landed on master since v0.1.112

Release commit

  • fb03370 release v0.1.113 — version fields only (package.json + package-lock.json).

Pre-flight (run against acp-kernel 0.0.71)

  • npm run typecheck ✅
  • npm test ✅ — 1595 tests / 1593 pass / 0 fail / 2 skipped
  • npm run build ✅ — acp-kernel inlined into dist

On merge

.github/workflows/release.yml runs npm ci + typecheck + test + build, then publishes to npm, tags v0.1.113, and creates the GitHub Release.

@github-actions

github-actions Bot commented Sep 15, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-15_release-v0.1.113 (580d835)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-795

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

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr795.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] 🏷 Verifying this release PR now — not re-doing work, just auditing per release protocol:

Verified so far

  • Release branch 2026-09-15_release-v0.1.113 head fb03370 contains exactly two commits vs master: 2f43f26 (acp-kernel 0.0.70 → 0.0.71) + fb03370 (version fields only in package.json + package-lock.json). Diff is clean — every line is release-related.
  • acp-kernel pinned exactly ("acp-kernel": "0.0.71", no caret) ✅ and confirmed live on npm (npm view acp-kernel version → 0.0.71) ✅ — cross-repo dependency rule satisfied.
  • Local pre-flight at fb03370: typecheck ✅ / test ✅ (1595 / 1593 pass / 0 fail / 2 skipped, matches the numbers in the PR body) / build ✅ (acp-kernel inlined into dist).

One thing I'm fixing before you merge: the branch was cut from 36d407a, then #793/#794 (zero-usage abort fix) landed on master — so the PR currently shows behind. GitHub would still merge fine, but CI would then test a different tree than what's on the branch. I'm merging origin/master into the release branch (clean merge, no conflicts — only pulls in src/loop/core.ts, src/plugin.ts, tests/issue793-zero-usage-abort.test.ts), re-running pre-flight on the merged tree, and pushing so the branch's CI reflects exactly what v0.1.113 will contain. Will report back with results.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Verification complete — release v0.1.113 is ready to merge. ✅

What I verified

  • Branch 2026-09-15_release-v0.1.113 head fb03370: exactly two commits vs master — 2f43f26 (acp-kernel 0.0.70 → 0.0.71) and fb03370 (version fields only in package.json + package-lock.json). No stray content; diff is fully release-related.
  • acp-kernel pinned exactly ("acp-kernel": "0.0.71", no caret) and confirmed live on npm before this bump — cross-repo dependency rule satisfied.
  • Local pre-flight at fb03370: typecheck ✅ / test ✅ (1595 tests, 1593 pass, 0 fail, 2 skipped — matches the PR body) / build ✅ (acp-kernel inlined into dist).

Fix applied before merging
The branch was cut from 36d407a, then #793/#794 (zero-usage abort fix) landed on master, leaving the PR behind. I merged origin/master into the release branch — clean merge, zero conflicts, pulling in only src/loop/core.ts, src/plugin.ts, and tests/issue793-zero-usage-abort.test.ts — then re-ran pre-flight on the merged tree: typecheck ✅ / test ✅ (1603 tests, 1601 pass, 0 fail, 2 skipped) / build ✅, and pushed as 580d835. This guarantees the branch's CI tested exactly what v0.1.113 will contain (i.e., the release also ships the #793 fix).

Current state (just checked)

  • PR head: 580d835, base master @ 9071541
  • mergeable_state: clean, all 7 CI check runs on 580d835: success (test ubuntu 22/24, test windows 22/24, zero-token e2e, version-guard, build-artifact)

On merge: .github/workflows/release.yml will run npm ci + typecheck + test + build, publish to npm, tag v0.1.113, and create the GitHub Release. I can't merge PRs — system rules forbid it. Please merge yourself: #795

📝 中文摘要:release 分支原本落后于 master(切出后 #793 才合入),我已在分支上干净地合入 origin/master 并重新跑完全量预检(typecheck/test/build 全绿,1603 测试 0 失败)后推送为 580d835,CI 全部通过、mergeable_state 为 clean,可以合并。

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