Repository navigation
[PR] (ai: anthropic/claude-opus-4-6) fix(release): emergency release flag skip_ci_gate now takes effect on the fallback relea | (ai: anthropic/claude-opus-4-6) fix(release): 紧急发版开关 skip_ci_gate 在 fallback 发版 PR 路径生效(原来被静默忽略,白等最多 60 分钟 CI) - #5431
Merged
Merged
Conversation
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, #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)
Contributor
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.7698-pr.5431.8449295This exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr5431.tgz
npm install -g packageInstall instructions are refreshed on each push. |
…straight to npm (#5430) Owner request 2026-11-01: an emergency control even faster than skip_ci_gate. With raw_publish ticked the one-click run performs exactly > billion-context@0.1.210 prepare > node scripts/check-dist-ready.mjs dist-ready: OK (dist/ is present) added 619 packages, and audited 622 packages in 10s 99 packages are looking for funding run `npm fund` for details 59 vulnerabilities (1 low, 20 moderate, 35 high, 3 critical) To address issues that do not require attention, run: npm audit fix To address all issues possible (including breaking changes), run: npm audit fix --force Some issues need review, and may require choosing a different dependency. Run `npm audit` for details. + > billion-context@0.1.210 build > npm --prefix kernel run build && npm --prefix pi-subagents run build && tsup && node scripts/write-build-info.mjs && node scripts/check-dist-import-annotations.mjs && node scripts/check-dist-external.mjs > acp-kernel@0.0.176 build > npm run clean && tsup && tsc --emitDeclarationOnly > acp-kernel@0.0.176 clean > node -e "require('fs').rmSync('dist',{recursive:true,force:true})" CLI Building entry: src/index.ts, src/panel/index.ts, src/persist/index.ts, src/wire/index.ts CLI Using tsconfig: tsconfig.json CLI tsup v8.5.1 CLI Using tsup config: /home/dog/tmp/pingce/billion-context/kernel/tsup.config.ts CLI Target: es2022 ESM Build start ESM dist/chunk-CSGXYMD3.js 32.87 KB ESM dist/chunk-6ECDTFU5.js 2.02 KB ESM dist/panel/index.js 6.96 KB ESM dist/index.js 330.49 KB ESM dist/chunk-4SDIPO2M.js 24.33 KB ESM dist/persist/index.js 19.83 KB ESM dist/wire/index.js 77.25 KB ESM dist/chunk-CSGXYMD3.js.map 66.04 KB ESM dist/chunk-6ECDTFU5.js.map 4.38 KB ESM dist/panel/index.js.map 17.58 KB ESM dist/chunk-4SDIPO2M.js.map 77.59 KB ESM dist/persist/index.js.map 46.16 KB ESM dist/wire/index.js.map 211.47 KB ESM dist/index.js.map 795.54 KB ESM ⚡️ Build success in 47ms > billion-context-pi-subagents@0.2.2 build > tsup && tsc --emitDeclarationOnly CLI Building entry: src/index.ts CLI Using tsconfig: tsconfig.json CLI tsup v8.5.1 CLI Using tsup config: /home/dog/tmp/pingce/billion-context/pi-subagents/tsup.config.ts CLI Target: es2022 CLI Cleaning output folder ESM Build start ESM dist/index.js 465.56 KB ESM dist/index.js.map 1.32 MB ESM ⚡️ Build success in 80ms CLI Building entry: {"agent/dsh-native-client":"src/agent/dsh-native-client.ts"} CLI Using tsconfig: tsconfig.json CLI tsup v8.5.1 CLI Using tsup config: /home/dog/tmp/pingce/billion-context/tsup.config.ts CLI Building entry: src/claude-mcp-entry.ts, src/claude-native-bootstrap.ts, src/claude-subagent-hook.ts, src/index.ts, src/mcp.ts, src/agent/dsh-acp.ts, src/agent/dsh-compaction-gate.ts, src/agent/dsh-native.ts, src/agent/omp-native.ts, src/agent/omp.ts, src/agent/opencode-native.ts, src/agent/opencode.ts, src/agent/pi-native.ts, src/agent/pi.ts, src/kimi/bootstrap-hook.ts, src/kimi/native-mcp.ts, src/zcode/bootstrap-hook.ts, src/zcode/mcp-entry.ts CLI Using tsconfig: tsconfig.json CLI tsup v8.5.1 CLI Using tsup config: /home/dog/tmp/pingce/billion-context/tsup.config.ts CLI Target: es2020 CJS Build start CLI Target: node20 CLI Cleaning output folder ESM Build start CJS dist/agent/dsh-native-client.js 32.20 KB CJS ⚡️ Build success in 13ms ESM dist/claude-subagent-hook.js 840.00 B ESM dist/agent/dsh-acp.js 5.84 KB ESM dist/agent/dsh-compaction-gate.js 2.53 KB ESM dist/mcp.js 1.63 MB ESM dist/claude-mcp-entry.js 2.19 MB ESM dist/claude-native-bootstrap.js 2.17 MB ESM dist/agent/dsh-native.js 2.32 MB ESM dist/agent/opencode.js 2.34 MB ESM dist/agent/omp.js 2.31 MB ESM dist/kimi/bootstrap-hook.js 2.13 MB ESM dist/agent/pi.js 2.31 MB ESM dist/zcode/mcp-entry.js 2.21 MB ESM dist/zcode/bootstrap-hook.js 2.14 MB ESM dist/kimi/native-mcp.js 2.18 MB ESM dist/agent/omp-native.js 2.76 MB ESM dist/index.js 5.55 MB ESM dist/agent/opencode-native.js 5.25 MB ESM dist/agent/pi-native.js 5.72 MB ESM ⚡️ Build success in 457ms build-info: commit=89835ec4-dirty dist-import-annotations: OK dist-external: OK (drift guard and release-notes check still enforced) and then immediately: no typecheck, no tests, no CI lanes, no push to master, no release PR. Bookkeeping so the repo stays coherent afterwards: - git tag v{VER} pushed; GitHub Release created with a RAW EMERGENCY PUBLISH banner in its body - version-sync PR opened (branch emergency-sync-v{VER}-ts) converging master's package.json — until it merges, the next one-click aborts on the drift guard by design (master is one patch behind npm) - the push step is skipped, which leaves steps.push.outputs.direct / needs_pr empty and therefore deactivates every downstream dispatch / wait / release-PR / publish step in this job (no double publish) Unticked behavior unchanged on every step. YAML parse verified. Docs in reference/release.md (one-click section).
This was referenced Nov 1, 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.
The
skip_ci_gateemergency checkbox on the one-click release workflow only worked on the direct-push path. Since master has branch protection, real runs land on the fallback path (release branch + auto PR), where the checkbox was silently ignored: the run still dispatched all CI lanes and waited up to 60 minutes for them to go green. The 2026-11-01 v0.1.211 release got stuck exactly here (#5424).What changes
.github/workflows/release-manual.yml:skip_ci_gateis ticked (before: always ran).if:only checkedneeds_pr == 'true'— this is the step that swallowed the whole wait and made the "emergency" button behave like a normal release.::warning::… permanent audit record of the bypassline): condition widened from direct-only to direct-OR-fallback.Un-ticked behavior is byte-for-byte unchanged: every step keeps its original condition plus a conjunct that is true by default. No kernel/** change, no new config field, no wire/session surface touched — workflow YAML plus one docs section in reference/release.md.
Compression both-modes: not applicable (no compression-decision code touched). Preflight gate: not applicable (CI/docs-only diff); validated locally with YAML parse + guard inventory.
Refs #5430. Unblocks future one-click emergencies only — the already-opened #5424 is unaffected by this PR (workflow files are read at dispatch time).
Added after review (same PR):
raw_publishnuclear buttonPer owner request, the workflow now has a SECOND checkbox: raw_publish. Ticked, the run does exactly
npm ci+npm run build(drift guard + release-notes check still enforced) and thennpm publishimmediately — no typecheck, no tests, no CI lanes, no push to master, no release PR. It pushes the git tag, creates the GitHub Release (body carries a RAW EMERGENCY PUBLISH banner), and opens a version-sync PR to converge master (until merged, the next one-click aborts on the drift guard by design). Implementation note: skipping the push step leaves its outputs empty, which deactivates every downstream dispatch/wait/release-PR/publish step — there is no second-publish risk. Both checkboxes default false; routine releases are byte-for-byte unaffected.