Skip to content

release v0.1.114 - #802

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

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

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Release v0.1.114 of billion-context.

Changes since v0.1.113

Dependency bump

  • acp-kernel 0.0.71 → 0.0.72 (exact pin). Kernel v0.0.72 ships tool-pair integrity fixes (acp-kernel release v0.1.58 #296): never split a tool call/result pair across a fold, and never split an assistant run that carries a fold anchor — avoids orphaned tool outputs on the wire after a compression fold.

Other changes merged to master since v0.1.113

Pre-flight (run against acp-kernel 0.0.72)

  • npm run typecheck — clean
  • npm test — 1611 tests, 1609 pass, 0 fail, 2 skipped
  • npm run build — success (dist/index.js 2.87 MB, kernel inlined)

Commits on this branch (over master)

  • 29f61aa deps: bump acp-kernel 0.0.71 -> 0.0.72
  • 93b2528 release v0.1.114

On merge, CI (release.yml) runs npm ci + typecheck + test + build, publishes to npm, tags v0.1.114, and creates the GitHub Release.

@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-15_release-v0.1.114 (93b2528)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-802

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

Option B — Download artifact

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

Install instructions are refreshed on each push.

@ranxianglei
ranxianglei merged commit a1b24aa into master Sep 15, 2026
7 checks passed
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Verified the release PR (#802, branch 2026-09-15_release-v0.1.114):

  • Diff is clean: exactly 2 commits over master (29f61aa deps bump acp-kernel 0.0.71 → 0.0.72 exact pin; 93b2528 release v0.1.114). Only package.json + package-lock.json touched — nothing bundled into the release commit.
  • Cross-repo dependency OK: npm view acp-kernel version → 0.0.72 is live on npm, so CI's npm ci will resolve.
  • Not yet published: registry still shows billion-context@0.1.113, as expected before merge.
  • CI: test (ubuntu-latest, 24) / test (ubuntu-latest, 22) / version-guard / build-artifact / codex zero-token e2e all green; two Windows test jobs were still running at check time.

Running my own local pre-flight (typecheck + full test suite + build) against the branch now — will follow up with results and the final CI status. Merge stays human-side per repo rules.

@ranxianglei
ranxianglei deleted the 2026-09-15_release-v0.1.114 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