Skip to content

[PR] ci: 恢复紧急快速发布入口(fast 模式加双信号防误触门) - #5054

Merged
ranxianglei merged 1 commit into
masterfrom
2026-10-28_restore-fast-mode-dispatch
Oct 28, 2026
Merged

ranxianglei merged 1 commit into
masterfrom
2026-10-28_restore-fast-mode-dispatch

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

(ai: anthropic/claude-opus-4-8)

Fixes #5053

这是什么

把 2026-10-25 被整体删除的 release-bugfix.yml 手动 dispatch 入口按紧急阀的本来面目恢复回来,并加固。原 fast mode(#3613 / commit 5de4103c,2026-10-18)是为"CI flakes 卡死正常发布通道"留的人为泄压阀——当年就是靠它救出的 v0.1.199;删除它的是 #4718 处置(207698b9:一个并发 agent 会话滥用手动 dispatch、在既定流程外发出了 v0.1.208)。本次为 owner 2026-10-28 明确指示的恢复。

改动(全部在一个工作流文件 + 一段文档)

.github/workflows/release-bugfix.yml:

  1. 入口恢复:重新声明 on.workflow_dispatch,带两个输入:fast(复选框)+ confirm_fast(文本框)。
  2. 双信号门(对 Incident record: A concurrent AI session bypassed the expected workflow and released v0.1.208 (the bugfix lane mechanism | 事故记录:并发的 AI 会话绕开预期流程发布了 v0.1.208(bugfix 车道机制已于当日拆除,待重建) #4718 的回归防护):fast 模式只在"勾选 fast 且 confirm_fast 逐字输入 FAST PUBLISH CONFIRMED"时生效;两个条件在 job 级求值一次进 env.FAST_ON,四个步骤门控(dispatch 矩阵 / 全量 pre-flight / fast-sanity / Full CI gate)统一引用。只勾一半、留空、或任何程序化点火 → 静默走原慢安全路径。手打确认短语是 agent 批量点火天然不会带的信号。
  3. 审计:fast 步骤的 warning 注解记录 github.actor。
  4. 头注释更新,写明 10-25 删除与 10-28 恢复的来龙去脉。
  5. 幸存的步骤级 fast 门控(:192-245 起,即 Stale docs & dead CI code left by the bugfix-lane workflow_dispatch removal | 删除 bugfix 应急 workflow_dispatch 后文档与 CI 残留未清理 #4842 所指 dead code)机制零改写,仅把条件从直接读 inputs.fast 改为读 env.FAST_ON——这正是"删了入口但没删机制"的现状,本 PR 让它名实相符。

reference/release.md:Emergency fallback 段更新为双信号语义(该段自入口删除起一直是陈旧描述,属 #4842 范围)。

不跳过的东西(与当年一致)

所有版本守卫(monotonic / not-already-live / sub-0.1.0 禁发)、plugin manifest 一致性(#4449)、release-notes 门禁(#1870)、npm ci + typecheck + build 健全性检查——一个都不少。跳过的只有全量 CI 矩阵派发/等待和本地全量 npm test,风险由点按钮的 owner 自担(描述文案明示)。

验证

  • YAML 解析通过(python yaml.safe_load,on 块 = pull_request + workflow_dispatch{fast, confirm_fast});
  • tests/release-ci-gate.test.ts 全绿(共享门禁脚本未动);
  • 非 dispatch 事件下 inputs.fast 为 null → FAST_ON=false,既有 PR-merge 发布路径行为不变;
  • 真实 dispatch 行为无法在本地演练,合并后第一次手动点火即是端到端验证(建议先用低版本目标试跑一次)。

范围边界

不碰 release.yml(普通通道的 #3539 自动复用是另一回事)、不碰 scripts/release-ci-gate.mjs、不改其他工作流。若后续想给普通 one-click 通道也加类似手动阀,另开 issue 讨论设计。

…n guard

Revives the #3613 / 5de4103 fast mode whose step gates survived 207698b's
dispatch removal as dead code (#4842): workflow_dispatch returns to
release-bugfix.yml as the emergency valve only. Fast mode now engages solely
when BOTH explicit signals arrive together (fast checkbox + confirm_fast
typed exactly FAST PUBLISH CONFIRMED), evaluated once into FAST_ON so any
default or programmatic dispatch keeps the slow safe path (#4718 guard).
The warning annotation records the acting user for the audit trail, and
reference/release.md's stale Emergency-fallback paragraph now states the
dual-signal semantics.
@ranxianglei
ranxianglei merged commit 5594c13 into master Oct 28, 2026
33 of 46 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-10-28_restore-fast-mode-dispatch (f7cebfb)

Latest build — install this exact version

npm install -g billion-context@0.0.6659-pr.5054.20e94d5

This exact version is immutable and reproducible. The rolling pr tag tracks the newest test build across all PRs.

Recent builds (commit → version)

commit version build
f7cebfb billion-context@0.0.6659-pr.5054.20e94d5 build

Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr5054.tgz
npm install -g package

Install instructions are refreshed on each push.

@github-actions

Copy link
Copy Markdown
Contributor

📦 Merged Build Published

This merge to master was published as 0.0.899-master.5594c13 (rolling master tag).

npm install -g billion-context@0.0.899-master.5594c13  # this exact build
npm install -g billion-context@master  # always the newest merged build

npm view billion-context@master prints the current version at any time.

@ranxianglei

Copy link
Copy Markdown
Owner Author

(ai: anthropic/claude-opus-4-8)

补充提交 2fbab5f(小问题直接修):同批审查发现 retired train 复选框的描述文案仍指向已不存在的 release-bugfix.yml pull_request_target 发布器(2026-10-25 车道重组后无任何工作流声明 pull_request_target)——#4842 所指 stale code 的一处。已将描述与报错文案改写为只陈述事实:此框永久拒绝,取消勾选即为普通 one-click 发布,通道见 reference/release.md。

@ranxianglei ranxianglei changed the title ci: 恢复紧急快速发布入口(fast 模式加双信号防误触门) [PR] ci: 恢复紧急快速发布入口(fast 模式加双信号防误触门) Oct 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant