Repository navigation
release v0.1.175 - #1739
release v0.1.175#1739github-actions[bot] wants to merge 2 commits into
Conversation
[bot] 🏷 中文摘要:这个 release PR 是纯版本号 bump(0.1.174→0.1.175),代码与 changelog 已逐项核对无误,v0.1.174→HEAD 版本区间回归审计未发现回归,内容上可以合并;唯一阻塞是 PR 的全部 CI runs 停在 Reviewed this auto-fallback release PR per the release-window audit protocol (②b). I did not redo any work — verification only. Merging stays human-only. ① Direction / provenanceAuto-fallback from the one-click workflow (run id 36673740079, 05:30Z): direct push to master was rejected with ③ Code audit (the PR diff itself)
②b Version-window regression audit (v0.1.174 → HEAD, 23 commits)Walked every fix/feat in the window against the pre-existing behavior each touched path carries:
None of the window's commits touch 本版本引入回归:无。 All behavior changes above are intentional and were disclosed in their respective PRs; this table doubles as the release-notes material. CI status — the actual blocker
|
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.1698-pr.1739.5e3a232This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr1739.tgz
npm install -g packageInstall instructions are refreshed on each push. |
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.174
PAIRED正则吞掉最多 64 个字符的助手正文 #1720)