Repository navigation
release v0.1.113 - #795
release v0.1.113#795
Conversation
…-trip fix; kernel release v0.0.71)
📦 Built Package ArtifactBranch: Option A — Install from npm PR tag (recommended)npm install -g billion-context@pr-795Each push to this PR publishes a new version under the Option B — Download artifact
tar xzf billion-context-pr795.tgz
npm install -g packageThis comment is automatically updated on each push. |
[bot] 🏷 Verifying this release PR now — not re-doing work, just auditing per release protocol: Verified so far
One thing I'm fixing before you merge: the branch was cut from |
[bot] 🏷 Verification complete — release v0.1.113 is ready to merge. ✅ What I verified
Fix applied before merging Current state (just checked)
On merge: 📝 中文摘要:release 分支原本落后于 master(切出后 #793 才合入),我已在分支上干净地合入 origin/master 并重新跑完全量预检(typecheck/test/build 全绿,1603 测试 0 失败)后推送为 |
Release v0.1.113.
Changes since v0.1.112
Dependency bump
acp-kernel0.0.70 → 0.0.71 (2f43f26) — blankreasoning_contentround-trip fix (acp-kernel #295). Confirmed live on npm before this bump.Landed on master since v0.1.112
conversation_idfor MCP tools (#761 / feat: per-call conversation_id for MCP tools — let the model supply its session id #760): unified canonical session id for MCP tool routing; per-call conversation ids route without pre-registration.Release commit
fb03370 release v0.1.113— version fields only (package.json+package-lock.json).Pre-flight (run against acp-kernel 0.0.71)
npm run typecheck✅npm test✅ — 1595 tests / 1593 pass / 0 fail / 2 skippednpm run build✅ — acp-kernel inlined into distOn merge
.github/workflows/release.ymlrunsnpm ci+ typecheck + test + build, then publishes to npm, tagsv0.1.113, and creates the GitHub Release.