Repository navigation
release v0.1.163 - #1517
release v0.1.163#1517
Conversation
|
又合并了两个issue进来注意 |
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.1458-pr.1517.d02c74dThis exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr1517.tgz
npm install -g packageInstall instructions are refreshed on each push. |
|
#1478 已经进入 |
[bot] 🏷 release v0.1.163 review (PR #1517) — audited against live master after the late merges you flagged. Late merges handled correctly:
Release-trigger sanity: Window audit v0.1.162..master (10 content commits, every diff reviewed): 本版本引入回归:无。 Behavior-change ledger (old → new):
Non-behavioral: MESSAGE-IDENTITY docs (#1506), ccr resend-semantics test assertions, 2-line comment cleanup. CI: prior head Everything checks out. Merge is human-only per repo rules: #1517 中文摘要:已审完 v0.1.162→v0.1.163 全窗口(含你提示的 #1499/#1506/#1478 三个后并入项),未发现回归;行为变更均为有意且已逐条列明,分支相对 master 只剩版本号改动,CI 全绿(测试矩阵收尾中),可以合并。 |
[bot] 🏷 CI follow-up for head Nothing outstanding from my side — #1517 is ready for a human merge; merging it triggers the standard release.yml publish (v0.1.163 → npm 中文摘要:最终提交 0bff16a 的 CI 已全部转绿(含收尾的测试矩阵),无失败项,PR 可合并。 |
Auto-fallback from the one-click release workflow: direct push to master was blocked by branch protection. Merging this PR publishes via the standard release.yml flow.
Changes since v0.1.162