Repository navigation
[PR] release: hot-disarm the patch lane (v3 workflow file + temp version revert to 0.1.206) - #4671
ranxianglei wants to merge 1 commit into
Conversation
…to 0.1.206) EMERGENCY MIGRATION COMMIT, bypasses no direct... actually via reviewed PR as usual. Context: #4654 (v2 lane-side arming) was merged BEFORE the model moved to v3 gate-branch publishing. Under v2 rules, the NEXT merge into this lane would publish 0.1.207 without the advisory note or gate-branch review. This PR replaces the lane-side workflow with the v3 file (whose resolve path no-ops for lane-targeted closes) AND temporarily reverts package.json to 0.1.206 so that if the OLD v2 copy still governs this very merge (it executes the pre-merge base-side file), the monotonic guard refuses (0.1.206 == npm latest) and nothing ships. EXPECTED: this run goes RED at the publish guard. That red is the disarm working. Follow-up PR restores the 0.1.207 pre-bump (under v3 it is then a silent no-op).
7c37855 to
34aecbe
Compare
(ai: vllm-qwen/qwen3.8-27b) 查重: 不适用 —— 本条是系统转发的既有 PR #4671 冲突解决任务,非新条目;未新开任何 issue/PR。 冲突已解决:PR 分支 八问:
判定:冲突已解、分支干净(mergeable=True,等 CI 绿灯),可合并。PR: #4671 |
|
(ai: vllm-qwen/qwen3.8-27b) SUPERSEDED — please do not merge this PR. Opened as the hot-disarm vehicle for #4667; shortly after, lane Consequences:
Please close it (close rights stay with you per policy). Full incident state is tracked in #4667. |
(ai: vllm-qwen/qwen3.8-27b) 查重: 不重复 —— 本 PR 是 #4667 自触发事故的处置动作(follows #4654 arming),无其他并行的 disarm 条目。相关项:#4659(master→lane 合并,改变了局面)、#4660(v3 finalize)、#4655(另一条同样指向该 lane 的 open PR,advisory force-install,范围不同)。 标签: bug, pr, scope/ci, p1(由 p2 改判 p1:事故域是「lane 上任何合并都可能把版本误发到 npm latest」,属核心能力停摆级风险;待 owner 确认处置后可降级) 核验结论:disarm 目标已由 #4659 达成;本 PR 现与 lane head 冲突,按现状合入会把 lane 的发布工作流文件回退到较旧快照。 核实的时序(均为 2026-10-25,+0800):
关键机制:同仓 PR 自身的 close 事件执行的是合并后 base 侧副本(#4654 自触发即实证)。v3 文件的触发面只覆盖 branches 本 PR 现状(本地实测):
结构化八问:
选项对比:
等你拍板:A(直接关,推荐) 或 B(我 rebase 瘦身为纯版本回退)。合并/关闭权都在你手上,我不自行操作。 |
(ai: vllm-qwen/qwen3.8-27b) 收到,按 SUPERSEDED 处理,不推进合并(合并权也只在人手)。 核对我留下的分支实际状态,与你的判断一致:
按政策我不执行关闭,PR 保持 open 等你关。已补状态标签 |
Emergency disarm of the armed v2 lane after the #4667 self-fire incident (v0.1.207 was published BY the arming merge #4654 itself).
Single commit
7c378558fon top of the lane head, two parts:.github/workflows/release-bugfix.ymlwith the v3 gate-branch file — under v3, any close targeting this lane resolves to a millisecond no-op (only a same-repo ship PR with base=bugfix, head=bugfix-vX.Y.Zcan fire).package.json0.1.207 -> 0.1.206, so that IF the OLD v2 base-side copy still governs this very merge event, the monotonic guard refuses (0.1.206 is not newer than npm latest 0.1.207) and nothing ships.Expected CI behavior: this merge's own publish run may go RED at the version guard depending on which copy governs the event — that red is the disarm working, exactly as stated in the commit message. Nothing publishes under either path. A follow-up restores the 0.1.207 pre-bump once the epoch-1 transition moves forward (under v3 it is then a silent no-op until a ship PR fires).
Verified observation (non-blocking): the v3 file carried here predates three fix commits that landed on master via #4660 (
843a37faegate-head shapes through version-guard,e9b8c0541publish/auto-cut shell defects,85c9a5ee8P4 lane-scan fork point). All three touch paths that are INERT for this disarm's purpose (no ship-shaped PR can exist yet — thebugfixgate branch does not exist), so merging as-is fully disarms the lane. Syncing the file to master's current copy is a trivial optional follow-up.Follows #4667 (removes the armed-lane exposure; the remaining epoch-1 steps are owner actions listed in that thread).