Skip to content

release v0.0.56 - #210

Merged
ranxianglei merged 1 commit into
masterfrom
2026-09-07_release-v0.0.56
Sep 7, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-09-07_release-v0.0.56

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Ships #182 (panel label fixes: never-shrinks wording, cumulative tokensCompressed).

Contents since v0.0.55:

After merge, release.yml publishes 0.0.56 to npm automatically. Then billion-context-pi #268 (already rebased onto v0.1.58, CI green) can merge; a follow-up bcp PR will bump the kernel dep to 0.0.56.

@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown

📦 Built Package Artifact

Branch: 2026-09-07_release-v0.0.56 (c600432)

Option A — Install from npm PR tag (recommended)

In your adapter project:

npm install acp-kernel@pr-210

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

Option B — Download artifact

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

This comment is automatically updated on each push.

@ranxianglei
ranxianglei merged commit 44eece8 into master Sep 7, 2026
4 checks passed
@ranxianglei

Copy link
Copy Markdown
Owner Author

Correction to the release note above: #182 also included a behavior fix beyond the label changes — syncBlocks now keeps host-expanded (user-decompressed) blocks inactive so restored messages are not re-folded next turn (double cost + lost originals); a fresh compress of the same range creates a NEW block. Full details in billion-context-pi#318 which bumps the dep.

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