Skip to content

[PR] release: arm merge-gated lane publish (lane-side release-bugfix.yml) - #4654

Merged
ranxianglei merged 1 commit into
bugfix-v0.1.206from
merge-gated-publish-arm
Oct 25, 2026
Merged

ranxianglei merged 1 commit into
bugfix-v0.1.206from
merge-gated-publish-arm

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

What

Lane-side copy of release-bugfix.yml v2 (identical file to #4653 on master) so that merging a reviewed PR INTO this lane becomes the release action for v0.1.207 (per the 2026-10-25 owner decision; the backport-ship label auto-publish is decommissioned).

Why this order is safe ("armed, not fired")

GitHub executes the BASE (lane-side) workflow copy for pull_request_target events. At the moment THIS PR merges, the event still runs the old lane-side yml (no such trigger) → nothing publishes. From the next merge onward, the new copy governs: a merged same-repo PR into this lane publishes its POST-MERGE head (= merge_commit_sha) through the full guard chain, then auto-opens the alignment PR to master. Non-merged closes no-op within milliseconds; fork PRs are rejected.

Diff

.github/workflows/release-bugfix.yml only (+156/−42 vs the lane's pre-#4596 copy: legacy closed-PR path kept dormant, all version guards / full-CI dispatch+wait / fast mode unchanged, label trigger removed, p_r_target + drift warning + audit comment + auto-alignment-PR added).

Suggested sequence (owner)

  1. Apply branch protection to bugfix-v0.1.206 (same status as master; payload in [PR] release: v3 gate-branch publish model (ship PR lane→bugfix fires; auto-cut next lane) #4653 thread).
  2. Merge this PR (arm).
  3. Merge the advisory-note PR — its merge fires the v0.1.207 publish (first round of the v2 flow; guards verify 0.1.207 > npm latest 0.1.206 before anything happens).

…bugfix.yml v2)

Same file as master's f009043 (#4653). GitHub executes the BASE (lane-side)
copy for pull_request_target events, so this must land on the lane BEFORE the
first merge-gated publish can fire. This merge itself cannot publish (at merge
time the event still runs the older lane-side copy, which has no such trigger):
armed, not fired.
@ranxianglei ranxianglei changed the title release: arm merge-gated lane publish (lane-side release-bugfix.yml) [PR] release: arm merge-gated lane publish (lane-side release-bugfix.yml) Oct 25, 2026
@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

查重: 不重复——本 PR 是 owner 2026-10-25 决策(v2 合入门控发布流)的 lane 侧武装件,与 #4653(master 侧同款文件)、#4655(advisory bc-2026-001,首轮流载体)同属一个发布闭环,三者互补不重叠。

已按 [PR] 流程核对代码与 CI(未重做工作),八问如下:

  1. 是什么问题/需求: 把「合并进 lane = 发版」的 v2 流程装到 bugfix-v0.1.206 lane 上(lane 侧 release-bugfix.yml v2),同时退役 backport-ship 标签自动发布——让人的 merge 按钮成为唯一发布触发器。
  2. 原因: 标签触发发布没有人工合并决策这道门([PR] fix(release): label-gated head-tree publish for conflicted carve-out ship PRs #4596 路径的设计缺陷);owner 拍板改为「受审 PR 合并进受保护 lane 即发布 post-merge lane head」。
  3. 影响范围与严重程度: 仅影响本仓库发布管道。武装前零行为变化——本 PR 自己的合并不触发任何发布(GitHub 对 pull_request_target 执行 BASE 侧旧 yml,旧文件无此 trigger,已核实);从下一次合并起新副本生效,每次并入 bugfix-v* lane 的合并都会走完整 guard 链。无用户端影响。
  4. 怎么修的: 新增 pull_request_target: closed → ["bugfix-v*","bugfix-release/**"] 触发;resolve 步硬性要求 merged=true + same-repo(fork 直接 reject)+ base 名匹配,发布对象 = merge_commit_sha(受审的 post-merge 状态);lane head 漂移只告警不改发布物;发布后审计评论 + 幂等自开 alignment PR(lane→master)。legacy closed-PR carve-out 路径保留 dormant。
  5. 回归审查(逐项): 既有行为清单全部过了一遍——版本单调性/未重发/sub-0.1.0/fork 拒绝等 publish guard:未动;Full CI dispatch+wait、fast 模式:逻辑未动(仅注释更新);legacy bugfix-release/* → master 关闭路径:保留可用。新增面:[PR] feat: Codex Desktop Plugin (Git marketplace + MCP tools + version sync) | feat: Codex 桌面版插件(Git marketplace + MCP 工具 + 版本同步) #4449 manifest 同步检查(与 release.yml 对齐,pre-[PR] feat: Codex Desktop Plugin (Git marketplace + MCP tools + version sync) | feat: Codex 桌面版插件(Git marketplace + MCP 工具 + 版本同步) #4449 tree fail-open 带 notice)、pull-requests: write 权限(仅用于审计评论 + alignment PR)。一处措辞小勘误(不影响代码):PR 正文说「label trigger removed」,但 lane 基线本来就没有 label trigger(标签路径只在 [PR] fix(release): label-gated head-tree publish for conflicted carve-out ship PRs #4596 后的 master 侧),净效果一致,v2 文件确认无任何 label 路径。未发现回归。
  6. 是否破坏缓存: 不涉及。
  7. 设计方向: 无转向——执行既定 owner 决策;文件与 [PR] release: v3 gate-branch publish model (ship PR lane→bugfix fires; auto-cut next lane) #4653 master 侧副本逐字节一致(diff 为空,已验证)。
  8. 新配置: 无(env/config/CLI 均无变化,纯 workflow)。

验证证据: 单文件 commit(+156/−42,与正文声明一致)✓ · 与 #4653 逐字节相同 ✓ · YAML 解析通过(triggers: pull_request / pull_request_target / workflow_dispatch)✓ · head e27471e33 CI 全绿(gate 全过,e2e lanes 按 path filter 跳过,符合预期)✓ · mergeable/clean ✓。

建议序列确认(与正文一致): ① 给 bugfix-v0.1.206 上分支保护(载荷在 #4653 thread)→ ② 合并本 PR(武装)→ ③ 合并 #4655(触发 v0.1.207 首发,guards 先验 0.1.207 > npm latest 0.1.206)。另注:#4653(master 侧副本)也应一并合并,否则后续从 master tag 切的新 lane 不会带 v2 流程;②③之前完成即可,②③之间顺序不限。

判定: 审核通过,可合入——等你按序列执行(分支保护 → 合并本 PR)。

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

(ai: vllm-qwen/qwen3.8-27b)

标签: scope/ci + p3(发布管道 workflow 武装件,非缺陷、无客户端车道;合并前零行为变化故 p3)。

@ranxianglei
ranxianglei merged commit 7e69b49 into bugfix-v0.1.206 Oct 25, 2026
30 of 45 checks passed
ranxianglei added a commit that referenced this pull request Oct 25, 2026
[PR] release: land the TRUE v3 gate-branch publish model (v2 arm self-fired at #4654)
ranxianglei added a commit that referenced this pull request Oct 25, 2026
…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).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant