Repository navigation
[PR] ci: remove the bugfix-lane/backport release machinery - #4719
Merged
Merged
Conversation
… + backport + lane-leak-guard) Owner-directed takedown 2026-10-25: a concurrent agent session abused the merge-gated lane shape to publish v0.1.208 outside the intended flow. All bugfix* branches and the patch-train ruleset are already deleted; this removes the armed workflow copies from master so no PR/dispatch against them can fire. Normal releases (*.release.yml / *_release-v* lanes) are untouched.
Contributor
📦 Built Package ArtifactBranch: Latest build — install this exact versionnpm install -g billion-context@0.0.5747-pr.4719.93a4bfeThis exact version is immutable and reproducible. The rolling Recent builds (commit → version)
Download artifact
tar xzf billion-context-pr4719.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.837-master.9f897ea # this exact build
npm install -g billion-context@master # always the newest merged build
|
ranxianglei
added a commit
that referenced
this pull request
Oct 25, 2026
…ne-system [PR] ci: restore the pre-backport carve-out channel (shipped out of #4719 by merge timing)
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: zhipuai-lb/glm-5.3)
Fixes #4718
Owner-directed takedown of the lane/backport release machinery (incident 2026-10-25, see issue) — final shape per owner: retain the pre-backport carve-out channel, everything else removed.
Deleted:
.github/workflows/backport.yml— label-driven auto carry PRs onto patch lanes..github/workflows/lane-leak-guard.yml— guard for the now-deleted lane branches.Replaced:
.github/workflows/release-bugfix.yml→ restored to its pre-backport form (last state ate5183631f8, i.e. the trusted #2011/#2851 carve-out publisher incl. #4449 manifest gate + full-CI pre-publish lanes), with theworkflow_dispatchtrigger removed. Only ignition shape left: a human merges abugfix-release/*PR against master.Already done outside this PR: all 7
bugfix*remote branches deleted, ruleset 25764850 (patch-train protection) deleted.NOT touched:
release-manual.yml(train mode already self-retires; remaining manual-publish path = separate owner decision, flagged in the issue),ci.ymlbranch filters and the version-guard whitelist (bugfix-release/*stays whitelisted — it's exactly what the retained channel needs), normal release flow (*_release-v*+release.yml) unchanged.