Repository navigation
[PR] release: v3 gate-branch publish model (ship PR lane→bugfix fires; auto-cut next lane) - #4653
Conversation
…backport-ship label) Owner decision 2026-10-25: a publish action must be a human MERGE into a protected patch lane — the single-label 'backport-ship' auto-publish path is dangerous and is decommissioned (the label itself was already removed from the repo). release-bugfix.yml (v2): - drop the 'labeled' trigger entirely - new 'pull_request_target' closed trigger on bugfix-v* / bugfix-release/** bases: resolving the POST-MERGE lane head (merge_commit_sha, same-repo guard, non-merged closes no-op within milliseconds), cross-checked against the live lane ref with a drift warning - audit comment on the merged lane PR - NEW post-publish step: auto-open the alignment PR (lane -> master, deduped, failure flagged non-fatal) so master picks up shipped content; merging it completes the cycle - legacy one-off carve-out path (pull_request closed, bugfix-release/* heads) kept DORMANT byte-for-byte; all version/guard steps (monotonic guard, manifest check fail-open, full-CI dispatch+wait, pre-flight, fast mode) unchanged release-manual.yml: 'Release (one-click)' train mode RETIRED — it refuses at its first step; its direct-push mechanics predate protected lanes. Master-lane flow unaffected. reference/release.md: patch-lane channel rewritten around the governing rules (protected lane = same status as master, content only via reviewed PRs, merge IS the release, alignment PR closes the cycle), label path marked DECOMMISSIONED, CI wiring = the required-checks story (core matrix on lane PRs; FULL matrix at the exact publish sha inside the pipeline). Arming order note: GitHub executes the BASE (lane-side) workflow copy for pull_request_target events, so this file must land ON a lane through an ordinary carry PR before its first merge-trigger can fire (follow-up PR to bugfix-v0.1.206).
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.5699-pr.4653.9383716This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4653.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Lane branch-protection payload (step 2 of the sequence)Empirical basis (verified against the only PR ever merged into a lane, #4577): a lane PR produces exactly one green check context — Master today (for parity reference): PR-only (0 approvals), strict checks [test shards ubuntu/windows × 22/24], force+delete disallowed, enforce_admins=false. Recommended rule for PUT /repos/ranxianglei/billion-context/branches/bugfix-v0.1.206/protection
{
"required_status_checks": {
"strict": true,
"contexts": ["gate"],
"context_options": []
},
"enforce_admins": false,
"required_pull_request_reviews": { "required_approving_review_count": 0 },
"allow_force_pushes": { "enabled": false },
"allow_deletions": { "enabled": false }
}i.e. same posture as master, with the one context that lane PRs provably produce. If you later want stricter entry gating (e.g. more static gates), add only contexts that lane PR events demonstrably run — re-query the lane PR's commits/check-runs first. |
(ai: vllm-qwen/qwen3.8-27b) 查重: 不重复 — open/closed issue+PR 全检索:这是独立的发布流程变更 PR(前身是它取代的 #4596 label 路径,非重复);companion arm-PR #4654 是同一设计的配套动作,不是重复条目。 标签: scope/ci + p3(发布流水线流程收紧,无用户侧缺陷;不打 bug——这不是缺陷修复)。 结构化八问
Review findings 与已执行动作a) 缺陷: b) 文档与观测不符并已修正:reference/release.md 原 "CI wiring" 段称 lane PR 跑 CORE matrix 且「这就是 lane 保护强制的 required-checks」。实测(活证据 #4654,lane PR):其 head sha 上只有 c) d) 分支保护已代设并验证(你的 gh-guard 写不了,我走 API 落了): e) 版本状态核验(你的第 3 步可行性):npm latest = 0.1.206,最新 tag = v0.1.206;lane 上已带着旧 train flow 留下的未发布 bump commit f) CI 状态:原 head f009043 上 diff 相关检查(static-gates/guards/docs-sync 等)全绿;红的 6 个 test shard 与 master head 52567f1 完全同签名(继承性红,与本 diff 无关——diff 只碰 .github/workflows/* + reference/release.md)。已在 #4599 留一行记录,未另开 issue(政策)。我的两个 review commit 已推上 判定可合。两个 review commit(a 的缺陷修复 + b 的文档对齐)请一并收进 PR;合入后按你的顺序执行 arm-PR(#4654)→ advisory note PR(首发 v0.1.207)。继承性的 6-shard 红不构成本 PR 特有阻塞,#4599 跟踪。 |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.831-master.8b24d1f # this exact build
npm install -g billion-context@master # always the newest merged build
|
What changed vs the earlier draft on this PR
Model revision after owner decision (2026-10-25): publishing must be one exact explicit act — a reviewed ship PR
bugfix-vX.Y.Z→bugfixbeing merged into the standalone protected gate branchbugfix(same status as master). Merging carries INTO a tag lane publishes NOTHING (the v2 "any lane merge fires" behavior is gone); every other PR shape is a millisecond no-op. Three files:.github/workflows/release-bugfix.yml— dual-path rewrite (pull_request_target closed, base ∈ {bugfix,master}):bugfix∧ head matchesbugfix-vX.Y.Z∧ same-repo ∧ merged → publish the POST-MERGE lane head (=merge_commit_sha, drift-checked against the live lane ref) through the unchanged guard chain (monotonic vs npm latest / not-already-live / no sub-0.1.0 / manifest fail-open notice / release-notes opt-in / full-CI dispatch+wait at the publish sha / npm ci + typecheck + full test + build) → tag → npm publish → GH Release → audit comment on the ship PR → auto-open alignment PR (head=bugfix→ master, title contract below).bugfix, base=master, same-repo, title starts withalign master with vX.Y.Z (shipped from) → auto-cut lanebugfix-vX.Y.Zfrom tagvX.Y.Z, pre-bump package.json +1 patch, push (idempotent; failure posts manual recovery commands AND fails loudly). One remaining manual click per cycle: applying branch protection (GITHUB_TOKEN cannot; announcement comment carries it).pull_requestclosed carve-out path kept dormant verbatim;workflow_dispatch fast=trueemergency escape hatch unchanged; concurrency group unchanged..github/workflows/ci.yml—bugfixadded to push+pull_request branch lists; the plan job forces FULL matrix scope for base=bugfix(born full-scope like Release PRs should default to running the full matrix: theci:fulllabel has a merge-timing race condition (v0.1.200's | 发版 PR 应默认跑全量矩阵:ci:full 标签存在合并时序竞态(v0.1.200 全量被取消后白付两遍) #3688 release PRs, no label needed). E2E lanes stay label-gated: the ship PR carries the standardci:fulllabel at open time, so they ride green.reference/release.md— gate-branch model v3: roles ofbugfix(THE GATE) / tag lanes / master; cycle stages P1–P4; alignment title contract (load-bearing for P4); protection PUT payload + the "required context roster comes from the PR's own check-runs" rule (a required context landingskippeddeadlocks merges); dual-lane section aligned (auto-cut replaces manual cut-after-first; ship PR = lane→bugfix; CI wiring v3).After this merges (owner steps)
bugfixoff the post-merge master (it carries this exact workflow file — base-side copy executes, so there is no arming window).bugfix(Settings → Branches; payload in reference/release.md § Lane/gate-branch protection; start withcontexts:["gate"]).bugfix-v0.1.206→bugfixwithci:full→ its FULL runs double as the probe → I harvest the exact context roster → you widen protection to the full roster.bugfix-v0.1.207auto-cuts itself. Cycle closed.Note: the advisory-note PR (#4655, into the lane) is a plain carry now — merge it into the lane BEFORE the ship PR is opened so the banner rides the release tree.
backport-shipstays decommissioned; the only labels the flow uses arebackport(carry routing) andci:full(e2e gate).