Repository navigation
[PR] release v0.1.211 - #5424
github-actions[bot] wants to merge 1 commit into
Conversation
(ai: vllm-qwen/qwen3.8-27b) 查重: 不重复 — 这是 one-click release 流程在直推 master 被分支保护挡下后自动回落生成的 v0.1.211 发版 PR(上游 #5424),open/closed issue 与 PR 中无同版本号的重复条目。 标签: pr(已有)+ scope/ci + p3 — 例行补丁发版,非缺陷报告;客户端标签不打:窗口内的改动(统一存储漂移自愈、kernel nudge 节奏、博客文档)都是跨车道通用面,不归属单一客户端。 已核对发版提交本身: 正在执行 v0.1.210..master 全窗回归审计(分段通读完整 diff、高危域精读),结论按结构化八问跟进在本线程。 |
(ai: vllm-qwen/qwen3.8-27b) Review 结论:本 PR 不应合并——建议关闭。 它已被更早的发布车道上游 PR #5419(同一版本 v0.1.211,今日 09:47Z 已合入 master)完全取代。本 PR 的树与当前 master 只差 4 个存储 golden 快照文件(旧摘要值);合入会把快照回退到旧形状、把测试车道重新打红。按先来后到保留 #5419、关闭后到的本 PR——关闭权在你。 查重: 与上游 PR #5419 100% 重复——同版本号、同基线内容(v0.1.210 以来的全部变更一致),#5419 另含两个 golden 再生提交且已合并。已补 八问
本次 CI 红的根因(供总控参考):#5415 落 kernel 时没有再生存储 golden → master born-red(8 例:4 条 wire 的 storage-render golden + 4 条 wire 的 full-mode restart proof,失败签名 一键流程观察(供参考):目前还挂着孤儿切出分支 标签:duplicate(与 #5419 同机制:同一版本的发布车道,先到者已合入);原有 pr / scope/ci / p3 保留。 收工判定:不合入,建议由你关闭本 PR;v0.1.211 的发布以 #5419 的 Release run 为准。 |
…#5430) The emergency checkbox was only honored on the direct-push path; when branch protection forced the fallback path (the common case) the run still dispatched the full lane set and waited up to 60 minutes, so one-click emergency release was unusable (v0.1.211 stuck on 2026-11-01, ranxianglei#5424). - guard 'Dispatch full CI on fallback branch' and 'Wait for full CI green on fallback branch' with !inputs.skip_ci_gate (same fast-mode semantics as confirm_fast in release-bugfix.yml: bypass = dispatch AND gate both skipped) - widen the audit-warning step to direct OR fallback path - stamp the auto-opened fallback PR body with an EMERGENCY BYPASS banner so whoever merges knows the sha shipped without lane verification - document the bypass in reference/release.md (one-click section)
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.210