Repository navigation
[PR] release: land the TRUE v3 gate-branch publish model (v2 arm self-fired at #4654) - #4660
Conversation
… next lane on alignment merge) - release-bugfix.yml: THE FIRE is now exactly one PR shape — a same-repo MERGED PR base=bugfix head=bugfix-vX.Y.Z publishing its post-merge lane head. Merging carries INTO a lane publishes nothing (kills the 'any merge into the lane ships' hazard). Second path: a merged alignment PR (head=bugfix, base=master, title contract 'align master with vX.Y.Z (shipped from <lane>)') AUTO-CUTS the next lane bugfix-vX.Y.Z from tag vX.Y.Z with package.json pre-bumped +1 patch (stage P4; idempotent; failure posts manual recovery and fails loudly). Alignment PR now heads from bugfix -> master. All version guards / full-CI dispatch+wait / fast dispatch escape hatch / legacy dormant carve-out path unchanged. - ci.yml: 'bugfix' added to push+pull_request branch lists; plan scope forces FULL matrix for base=bugfix ship PRs (born full-scope like #3688 release PRs). e2e lanes are label-gated (ci:full), so the ship PR gets that label at open time — no e2e yml changes needed. - reference/release.md: gate-branch model v3 (roles of bugfix / tag lanes / master, P0-P4 cycle, alignment title contract, protection payload incl. context-roster rule), dual-lane section aligned (auto-cut, ship PR lane->bugfix, CI wiring v3).
…nd why v3 has no arming step
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.5708-pr.4660.fa7e95dThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4660.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm/qwen3.8-27b) 查重: 不重复 — searched open+closed issues/PRs for "gate-branch" / "arming" / "release-bugfix": this PR (#4660) is the only open item on the v3 gate-branch publish model. Related but distinct lineage: #4653 (merged v2 lane-publish doc — the predecessor whose wide trigger caused the incident), #4654 (the arming PR that self-fired and published v0.1.207 — closed), #4659 (open companion: align master with the shipped v0.1.207 tree — different scope), #4477/#4500/#4467 (closed design discussions that led to the dual-lane model). 标签: This is a [PR] issue tracking existing PR #4660 (branch Now doing the full review of the trigger logic against the incident timeline; will post the structured verdict (eight questions) once the test shards finish. |
…4660) Review of the v3 model found the guard deadlocks the cycle at P3: the auto-opened alignment PR (head=bugfix, base=master) legitimately carries the shipped version bump into master, and backport carry branches inherit the lane pre-bump — neither shape matched the allowlist, so both would fail this guard on every cycle. Extend the allowlist with bugfix and backport/carry-* (ship lanes already pass via bugfix-v*).
Review of the v3 model found four defects in the new step shells: - MANUAL_CMDS ended in an unterminated single quote, so bash rejected the ENTIRE auto-cut script before it could run (P4 could never succeed). - the final notice referenced $NEW_lane under set -u (defined var is NEW_LANE) — an unbound-variable crash after the push already succeeded. - the drift warning compared the LANE head against the ship MERGE sha, which lives on `bugfix`, never on the lane — it would warn on every non-ff ship. Compare against the reviewed lane tip (ship PR head sha, threaded as a new resolve output) instead. - the cycle-close notice printed an empty $VER on publish paths (resolve only sets it for cuts); read it from the version step.
#4660) The epoch-1 transition (reference/release.md) cuts the first v3 lane from ALIGNED MASTER, whose window from the nearest tag contains ordinary post-tag master merges — the guard false-alarmed 'lane leak detected' and its rebuild-from-tag advice would re-inherit the stale pre-v3 workflow file (the self-fire hazard v3 removes). When the lane forked from master strictly after its base tag, rescan from the fork point. Simulated all four lane species: tag-cut clean / nested carve-out unchanged-green, master-cut now green, real master-merge still RED.
…from aligned master) The issue body states the design but the shipped doc never said how to get past the one stale artifact left by the incident: tag v0.1.207's tree carries the v2 wide trigger, and backport.yml auto-cuts a missing lane from the latest tag on demand. Add the ordered procedure (including the do-not-label-backport window and advisory bc-2026-001's frozen old target) plus the two accepted consequences of cutting from aligned master.
(ai: vllm-qwen/qwen3.8-27b) Review 完成:模型设计成立,但实现里找到 7 个缺陷——已全部修掉并推上 PR 分支(4 个独立标注 commit)。CI 的 test-shard 红是 master 继承性红,与本 PR 无关。 结构化八问:
行为变更披露(旧→新):
范围扩大披露:除 PR 原有 3 文件外,另改 CI 状态:新 head 观察项(未修,供参考):
判定:本 PR 自身门禁面全绿,test-shard 红为继承性(建议等 master 侧收敛后合并;若判断可接受也可直接合并——它是 workflows+docs 变更,不阻塞运行时)。我不能合并(系统规则:合并仅限人工):#4660 。合并后按 reference/release.md 的 Epoch-1 transition 章节执行第 2–7 步即可进入无 arming 循环。 |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.832-master.28b667b # this exact build
npm install -g billion-context@master # always the newest merged build
|
What this is
The true v3 document set (release-bugfix.yml dual path + ci.yml FULL-scope-for-bugfix + reference/release.md rules), developed as #4653 but merged before the v3 push landed: #4653 captured the pre-v3 head at 07:43:21Z, so master and every live tree still run the v2 wide trigger ("any same-repo merge into a bugfix-v* lane publishes").
Why it matters right now (incident, 2026-10-25 07:43–08:09Z)
Merging arming PR #4654 resolved its own
pull_request_targetclose event against the base ref after the merge landed → the arm triggered itself → run 40173869038 ran the full guard+CI chain and published v0.1.207 (tag = post-merge head7e69b49f, GH Release 08:09:37Z, npmbillion-contextnow 0.1.207). The shipped tree lacks advisory bc-2026-001 (#4655 never merged). The old lane is frozen by the monotonic npm guard — later closes into it die red at "not strictly newer than latest", zero npm churn — but the v2 doc still live on master would re-fire any future lane merge if a lane were ever cut from it again. Root cause documented in reference/release.md ("Why v3 has no arming step"): an arming commit whose trigger matches its own target fires itself.What changes
pull_request_target closedbranches[bugfix, master], dual resolve paths: A) PUBLISH on ship PR (base=bugfix, head=bugfix-vX.Y.Z) of the POST-MERGE lane head; B) AUTO-CUT next lane when the alignment PR (head=bugfix, contract title) merges into master. Every other close = millisecond no-op. Legacy carve-out stays dormant; fast dispatch retained; permissions/secret surface unchanged.bugfix; plan job forces FULL scope when PR base =bugfix(ship PRs run the complete suite; e2e lanes ride theci:fulllabel as before).Cycle impact after this lands
No arming ever again: the
bugfixgate branch is born carrying v3, tag lanes are cut from aligned master (which will then contain this doc), and only the one ship-PR shape can fire. Advisory bc-2026-001 rides into the next release (0.1.208).