Skip to content

release v0.0.62 - #243

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-10_release-v0.0.62
Sep 10, 2026
Merged

release v0.0.62#243
ranxianglei merged 1 commit into
masterfrom
2026-09-10_release-v0.0.62

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Release v0.0.62 — ships CoreMessage.thinkingTokens + countMessageTokens unified metering (#241 / PR #242): every per-message counting site (range recommendations, block compressedTokens, context breakdown, status report, ref-tag tokens attribute) now includes the host-projected thinking payload. Truncation gates keep the pure-text chars caliber. Optional field — hosts that do not attach it see zero behavior change.

@github-actions

Copy link
Copy Markdown

📦 Built Package Artifact

Branch: 2026-09-10_release-v0.0.62 (da450ed)

Option A — Install from npm PR tag (recommended)

In your adapter project:

npm install acp-kernel@pr-243

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

Option B — Download artifact

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

This comment is automatically updated on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 PR #243 review — release v0.0.62

Duplicate screening: searched open+closed issues/PRs for "release v0.0.62" — no other release PRs or duplicate requests. Not a duplicate.

Diff cleanliness (first gate):

  • Exactly 1 commit da450ed ("release v0.0.62") on top of current master tip 3c8b00c (merge of feat: CoreMessage.thinkingTokens — meter host-projected thinking payload #242, the thinking-tokens feature). No unrelated changes bundled in.
  • Changed files: package.json version 0.0.61 → 0.0.62 (1 line) + package-lock.json version fields synced (2 lines). This exactly matches the pattern of the two most recent releases (v0.0.60 23d1cde, v0.0.61 9f9f24f — both touched the same 2 files, same stat). Every changed line is the version bump itself; the lockfile delta is a pure version-field sync, not collateral churn. Clean.
  • Branch naming 2026-09-10_release-v0.0.62 ✅, commit message release v0.0.62 ✅, no prerelease suffix so CI publishes as latest ✅.
  • GitHub reports mergeable / clean (no conflict with master) ✅.

Pre-flight (real Node v22.23.2, per AGENTS.md §5):

  • npm run typecheck — clean
  • npm test — 638 passed, 0 failed
  • npm run build — success

Body claim spot-check: the shipped feature is present on this branch — CoreMessage.thinkingTokens?: number (src/types.ts:20), unified metering countTokens(text) + thinkingTokenValue(thinkingTokens) in countMessageTokens (src/tokenize.ts:39), and the ref-tag tokens attribute using the same caliber (src/render-refs.ts:81). Consistent with the description.

Nothing to fix directly — no commits added to the branch. Ready for a human to merge; I won't merge per repo rules. After merge, CI tags v0.0.62 and publishes.

中文摘要:审查通过——diff 干净(仅版本号 0.0.61→0.0.62,与最近两次 release 惯例一致)、typecheck/test(638)/build 全绿、功能代码确认在位,可以合并。

@ranxianglei
ranxianglei merged commit 9b790ec into master Sep 10, 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