Skip to content

release v0.0.54 - #204

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-06_release-v0.0.54
Sep 6, 2026
Merged

release v0.0.54#204
ranxianglei merged 1 commit into
masterfrom
2026-09-06_release-v0.0.54

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Version-only release bump for v0.0.54.

Changes since v0.0.53

  • PR#203 (c1634b1): fix report tool accounting — attribute tool-results to their calling tool via toolCallId map (#386 follow-up); pct() floor removed; uncompressed ranges label true dominant tool; isToolMessage exported and reused; panel docstrings stop claiming chars/4. 5 new regression tests (580/580).

Pre-flight

  • typecheck ✓
  • tests 580/580 ✓
  • build ✓

Downstream: billion-context will pin 0.0.54 and switch its 3 buildStatusReport call sites to defaultCountTokens (closes billion-context#386).

@github-actions

github-actions Bot commented Sep 6, 2026

Copy link
Copy Markdown

📦 Built Package Artifact

Branch: 2026-09-06_release-v0.0.54 (93d0df4)

Option A — Install from npm PR tag (recommended)

In your adapter project:

npm install acp-kernel@pr-204

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

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf acp-kernel-pr204.tgz
npm install ./package

This comment is automatically updated on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 ework agent · qwen3.8-27b

[bot] 🏷 Release PR audited — verified clean, ready for human merge.

Checks performed (all pass):

  1. Commit hygiene — single commit 93d0df4 release v0.0.54; diff vs master is exactly 1 file, +1/−1: package.json "version": "0.0.53" → "0.0.54". Nothing else bundled into the release commit.
  2. Base correctness2026-09-06_release-v0.0.54 sits directly on current master tip bf9f5a9 (merge of PR fix: report tool accounting — attribute tool-results to their tool #203, c1634b1 report-tool-accounting fix), matching the stated "Changes since v0.0.53".
  3. Conventions (AGENTS.md §5) — branch name YYYY-MM-DD_release-v{VERSION} ✓, commit message release v{VERSION} ✓, version-only change ✓, no prerelease suffix (publishes to latest) ✓.
  4. Pre-flight re-run locally on the release branch (Node v22):
    • npm run typecheck ✓ (tsc --noEmit, no errors)
    • npm test ✓ — 580/580 pass, 0 fail/skip/cancel
    • npm run build ✓ (tsup bundle + tsc --emitDeclarationOnly)
  5. GitHub API — PR release v0.0.54 #204 open, mergeable: true, mergeable_state: clean, base master, 1 commit, 1 changed file.

⚠️ Merging is human-only per repo rules — I can't merge PRs. Please merge yourself: #204

After merge, CI will tag v0.0.54 and publish to npm; verify with npm view acp-kernel version, then billion-context can pin 0.0.54 and switch its 3 buildStatusReport call sites to defaultCountTokens (closes billion-context#386).

@ranxianglei
ranxianglei merged commit a905b94 into master Sep 6, 2026
4 checks passed
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