Repository navigation
[PR] ci: 恢复紧急快速发布入口(fast 模式加双信号防误触门) - #5054
Merged
Merged
Conversation
…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.
Contributor
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.6659-pr.5054.20e94d5This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr5054.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Contributor
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.899-master.5594c13 # this exact build
npm install -g billion-context@master # always the newest merged build
|
Owner
Author
This was referenced Oct 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(ai: anthropic/claude-opus-4-8)
Fixes #5053
这是什么
把 2026-10-25 被整体删除的
release-bugfix.yml手动 dispatch 入口按紧急阀的本来面目恢复回来,并加固。原 fast mode(#3613 / commit5de4103c,2026-10-18)是为"CI flakes 卡死正常发布通道"留的人为泄压阀——当年就是靠它救出的 v0.1.199;删除它的是 #4718 处置(207698b9:一个并发 agent 会话滥用手动 dispatch、在既定流程外发出了 v0.1.208)。本次为 owner 2026-10-28 明确指示的恢复。改动(全部在一个工作流文件 + 一段文档)
.github/workflows/release-bugfix.yml:on.workflow_dispatch,带两个输入:fast(复选框)+confirm_fast(文本框)。confirm_fast逐字输入FAST PUBLISH CONFIRMED"时生效;两个条件在 job 级求值一次进env.FAST_ON,四个步骤门控(dispatch 矩阵 / 全量 pre-flight / fast-sanity / Full CI gate)统一引用。只勾一半、留空、或任何程序化点火 → 静默走原慢安全路径。手打确认短语是 agent 批量点火天然不会带的信号。github.actor。: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 自担(描述文案明示)。验证
tests/release-ci-gate.test.ts全绿(共享门禁脚本未动);inputs.fast为 null →FAST_ON=false,既有 PR-merge 发布路径行为不变;范围边界
不碰
release.yml(普通通道的 #3539 自动复用是另一回事)、不碰scripts/release-ci-gate.mjs、不改其他工作流。若后续想给普通 one-click 通道也加类似手动阀,另开 issue 讨论设计。