Skip to content

release v0.1.81 - #507

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-04_release-v0.1.81
Sep 4, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-04_release-v0.1.81

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Changes since v0.1.80

Both independently reviewed on the PR threads (incl. combined-tree pre-flight on post-0.1.80 master).

Pre-flight

  • typecheck ✅ · tests 1020/1022 (2 known env fails in plugin-agent.test.ts) ✅ · build ✅
  • Commit is version-bump only.

@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-04_release-v0.1.81 (ac2f9f3)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-507

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

Option B — Download artifact

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

This comment is automatically updated on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 ework agent · qwen3.8-27b

[bot] 🏷 Verified release PR #507 independently — checked out 2026-09-04_release-v0.1.81 @ ac2f9f3 and ran the full pre-flight myself rather than trusting the body.

Release mechanics — all correct

  • Branch 2026-09-04_release-v0.1.81 matches *_release-v*; tip commit ac2f9f3 message is release v0.1.81.
  • Version commit is isolated: touches ONLY package.json + package-lock.json, both 0.1.80 → 0.1.81 (exact bump, no prerelease dash).
  • acp-kernel pin unchanged → no cross-repo publish-ordering risk.
  • Full tree diff vs master is confined to the two fixes + CHANGELOG.md/CONFIGURATION*.md docs + the version bump. No stray changes, no lockfile drift beyond the version lines.

Pre-flight (my run)

  • typecheck ✅ (tsc exit 0)
  • build ✅ — dist/index.js 2.63 MB, self-contained (acp-kernel inlined)
  • tests 1021/1022 pass, 1 fail — and the single fail is environmental, not release-related: tests/launcher.test.ts › resolveClientCommand: codex/claude resolve to themselves. This sandbox has a codex executable on PATH, so the resolver returns an absolute path where the assertion expects the bare name. The release diff doesn't touch launcher.ts/client-config.ts, so it can't be release-introduced — same "known env fail" class you flagged (your env trips 2 in plugin-agent.test.ts; mine trips this one instead). No real regressions.
  • E2E (tests/e2e/e2e-codex.test.ts) not run here — it needs a live local upstream unreachable from the sandbox; your combined-tree pre-flight on post-0.1.80 master already covers it.

Content sanity — both fixes match their descriptions and are minimal + well-commented:

One heads-up for whoever presses merge: the release branch is master(v0.1.80) + merge #500(#496) + merge #502 + the version bump. So #500 and #502 have not been merged to master separately — landing #507 brings their content into master too. Consistent with how these bundled releases go, just noting it so the merge is fully informed.

Registry state: latest = 0.1.80; PR artifact built at pr-507 = 0.1.81-pr.507.330. v0.1.81 stays unpublished until the merge.

Verdict: well-formed, pre-flight clean (modulo the sandbox-only env fail). Ready to merge. Per AGENTS.md I can't merge PRs — this needs a human:
#507
On merge, CI publishes v0.1.81 automatically.

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