Repository navigation
[PR] Restore the emergency channel (raw_publish/skip_ci_gate) + fix the four feature regressions introduced by this revert (A | 恢复紧急通道(raw_publish/skip_ci_gate)+修掉这次回退带回来的四处功能损失(A–E) - #5447
Conversation
…5430) on top of the reverted flow, with four regressions fixed #5446 ('恢复老的ci release manal') restored the classic pre-flight npm ci + typecheck + build and dropped today's emergency buttons. Owner decision (2026-11-01, incident): keep BOTH — the old full-CI normal path AND the emergency channel. This restores release-manual.yml from 1115455 (the last state that had the channel, i.e. #5430-era workflow) and adds back the single line #5446 kept: npm ci inside the Pre-flight gate. Net effect vs master: A. skip_ci_gate + raw_publish inputs, Raw emergency publish step and all the if-conditions that wire them — back. Emergency = deps download + build + publish, zero CI, no master push, tag + GitHub Release + version-sync PR. B. Full CI dispatch again carries CI_FULL_DISPATCH=1 — direct releases dispatch the COMPLETE lane set at the publish sha, not ci.yml's CORE default (the #3539 windows/node24 gap #5446 reopened). C. Bump version syncs the plugin manifests via scripts/sync-codex-plugin-version.mjs and Verify bump diff accepts them again (#4449). D. job timeout-minutes: 90 is back — a wedged release run can no longer pin the one-click-release concurrency group for hours. E. Drift guard keeps its pending-bump state (#5376) instead of hard-failing whenever master leads npm by one patch. Plus the #5445 fix folded in: on the raw_publish path a master/npm version skew (the state right after emergency publish #1, before its version-sync PR merges) logs a loud audit warning instead of exit 1 — back-to-back emergency publishes work. The duplicate-publish guard (npm version already exists) stays. Verified: YAML parses; inline scripts of Drift guard / Raw emergency publish / Bump version pass bash -n.
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.7713-pr.5447.447d979This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr5447.tgz
npm install -g packageInstall instructions are refreshed on each push. |
(ai: vllm-qwen/qwen3.8-27b) 落地提醒:本分支的 Pre-flight gate 仍缺依赖安装行(继承 #5444 删掉的 修法在 #5448(与本分支同 base |
(ai: qwen/qwen3.8-27b) 查重:不重复。本 PR 是 #5430 紧急通道(曾合入、后被 #5446 回退)的重做,并把已关闭未合的 #5445(第二次紧急发版被 drift guard 卡死)一并收进来。相关链:#5430(原通道)/ #5446(回退老流程)/ #5445(被取代)/ #3539(全矩阵派发)/ #4449(manifest 同步)/ #5376(pending-bump)。基于含 #5446 的 master( 审核方式(独立性):没照抄 issue 结论。我独立读了回退后基线文件( A–E 逐项核实
发现(按严重度)
结构化八问
判定:方向对、A–E 主体成立、正常路径干净无回归;但紧急通道收敛机制有真缺陷(空同步 PR),会让每次应急发版后卡住普通发版且工具文案误导。建议先修掉发现 1(或明确降级为手动收敛并改文案)再合并;发现 2 死代码可顺手精简。全量 test lane 在跑(in_progress),本 PR 未改源码,与其无直接关系。 要我直接在这个 PR 分支上把发现 1 的修法①(补 commit)落地、并顺手删掉发现 2 死代码吗?因为是你的发版基建、又刚回退过一次的高敏区,我没擅自动手,等你拍板走哪个方案。 |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.989-master.9ddc5d1 # this exact build
npm install -g billion-context@master # always the newest merged build
|
…ncing Today's audit of the raw_publish emergency path (ranxianglei#5430/ranxianglei#5447) found two silent bookkeeping bugs in 'Raw emergency publish': the Bump version step stages the bumped package.json/changelog/manifests but never commits them (the commit lives in 'Commit and push to master', which the raw path skips), so in the raw workspace: 1. git tag v$VER pointed at a tree that still carried the OLD version — later bugfix-lane cuts-from-tag read the stale version from the tree and misfire their strict-newer/already-live guards; 2. git push HEAD:refs/heads/emergency-sync-... pushed a branch byte- identical to master -> empty diff -> GitHub rejects the auto sync PR with a 422 -> master never converges -> the next NORMAL one-click release aborts on the drift guard. Fix: commit the staged bump in-place right after npm publish, before any tag/branch push. The tag then points at a version-consistent tree and the sync PR carries a real mergeable diff (branch name still matches neither release.yml gate, so merging publishes nothing). On the pending_bump path the tree is already bumped, nothing stages, and the guarded commit no-ops with a notice.
一句话
#5446(恢复老流程)已经合并了,这个 PR 不推翻它:老的正常路径(npm ci → typecheck → build → 全量 CI lane 绿了才发)完整保留,在其之上把今天 #5430 的紧急通道加回来,并修掉回退时顺手弄丢的四处功能。最终效果 = 老流程 + 紧急按钮并存。
改动内容(单文件 .github/workflows/release-manual.yml)
raw_publish/skip_ci_gate两个勾选项 + 「Raw emergency publish」步骤(下依赖→build→publish→打 tag→GitHub Release→开收敛 PR,零 CI、不碰 master)+ 各步骤对应的 if 条件。事故时勾 raw_publish 即可直接发版。CI_FULL_DISPATCH: "1"。没有它 ci.yml 只跑 CORE 矩阵(scripts/release-ci-gate.mjs:302/305),windows/node24 专属回归可以发布出去——一键发版太慢:前置门单机串行跑全量测试 30-40 分钟,且同一套测试在发版链路里重复跑 2-3 遍 #3539 修过的坑被这次回退重开了。node scripts/sync-codex-plugin-version.mjs([PR] feat: Codex Desktop Plugin (Git marketplace + MCP tools + version sync) | feat: Codex 桌面版插件(Git marketplace + MCP 工具 + 版本同步) #4449),Verify bump diff 白名单同步恢复。不发这个,每次发版 .agents/.claude-plugin/plugins/codex 的 manifest 都停在旧版本,marketplace 更新检测会坏。timeout-minutes: 90。没有它一个卡住的发布 job 最长能挂 6 小时,占住 one-click-release concurrency 组,后面所有发布排队卡死。已验证
bash -nf248a9ef),无冲突,[PR] Emergency channel fix: after the first emergency release, the second one is no longer stuck. | 紧急通道修复:第一次紧急发版之后,第二次不再被卡死 #5445 已由本 PR 取代(我会关掉它)验证方式(合并后)