Skip to content

release v0.1.98 - #672

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

release v0.1.98#672
ranxianglei merged 1 commit into
masterfrom
2026-09-10_release-v0.1.98

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Release v0.1.98 — ships the compress-reasoning drop with round-evidence closure (#651, PR #667) and the MCP stale-conversation-id recovery (#657), both merged after v0.1.97 was cut. No acp-kernel bump (stays 0.0.61).

@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown

📦 Built Package Artifact

Branch: 2026-09-10_release-v0.1.98 (23bb229)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-672

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

Option B — Download artifact

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

This comment is automatically updated on each push.

@ranxianglei
ranxianglei merged commit c4c2e64 into master Sep 9, 2026
6 checks passed
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 Release v0.1.98 verified — all checks pass, publish in flight:

Release hygiene (all compliant):

Status:

  • Pre-merge CI on the branch: ✅ success (PR Build Artifact + CI green on 23bb229).
  • PR was already merged (by a human, 17:39:14Z) — per system rules I don't merge; nothing left for me to do there.
  • Post-merge Release workflow is in_progress on merge commit c4c2e64 (run 34384222982). As of my check, npm latest is still 0.1.97 and tag v0.1.98 not yet cut — expected while CI runs.

I'll follow up once v0.1.98 is live on npm and the tag exists.

中文摘要:release 分支/提交/版本号均合规(仅改 version,acp-kernel 保持 0.0.61),PR 已被人工合并,CI 发布流程进行中,待 npm 出现 0.1.98 后确认收尾。

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