Repository navigation
fix: allow bugfix-release/* carve-out branches in ci.yml version-guard - #2859
Conversation
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.3173-pr.2859.7e42b38This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2859.tgz
npm install -g packageInstall instructions are refreshed on each push. |
[bot] 🏷 PR review 完成 — 结论:可合并(人工 merge)。 核对范围:单 commit 独立验证(非转述 PR 描述):
八问:
CI 状态(head 合并后动作:re-run PR #2857 的 CI(pull_request 事件使用 base 分支的 workflow 定义,会拾取修好的 guard)即可转绿并发布 v0.1.195。 判定:可合并。涉及 CI workflow,按 §7.4 留人工 review/merge。 |
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.304-master.75b861c # this exact build
npm install -g billion-context@master # always the newest merged build
|
Closes #2858
What
#2853 made the bugfix carve-out channel PR-gated: the branch keeps the
bugfix-release/prefix as the carve-out marker (release-bugfix.yml publishes on the closed-PR trigger;release.yml/master-build.ymldetection regex^[0-9]{4}-[0-9]{2}-[0-9]{2}_release-vdeliberately does NOT match it). Butci.yml'sversion-guardstill only whitelisted*_release-v*, so every carve-out release PR — which legally carries exactly one isolatedrelease v{VERSION}bump commit — was rejected as a "non-release branch". First casualty: PR #2857 (bugfix-release/v0.1.195-dsh-compaction-422) red at head sha7c41abd29c8d, all other lanes green.Because
release-bugfix.yml's full-CI gate is fail-closed, a red version-guard also blocks the merge-time publish — the channel was effectively unusable until this lands on master.Fix
.github/workflows/ci.ymlversion-guard allowlist:*_*_release-v*→*_release-v* || bugfix-release/*(one condition + comment update).reference/release.mdcarve-out section: added the guard-compatibility requirement (the version-guard MUST whitelist the marker prefix) with the ci.yml version-guard 不识别 bugfix-release/* carve-out 分支:#2853 新通道下所有 carve-out 发布 PR 必红 #2858 divergence as the cautionary case, so the two files can't silently fork again.Deliberately NOT done: renaming carve-out branches to
*_release-v*to slip past the guard — that would makerelease.yml/master-build.ymlmisfire on merge and double-publish the post-merge master tree, the exact accident #2853's design prevents.Behavior change (flagged per policy)
CI gate semantics:
version-guardpreviously rejected ANYpackage.jsonversion diff on branches not matching*_release-v*; it now also passesbugfix-release/*branches unconditionally (same posture as release branches — the isolated-commit discipline is enforced by process/review, not by this guard, for both kinds). No impact on normal release, kernel release (*_release-kernel-v*was already outside the allowlist AND never diffs the root package.json's version field), or content branches.Verification
bugfix-release/v0.1.195-dsh-compaction-422→ allow;2026-10-12_release-v0.1.196→ allow;feature/*→ deny (unchanged); edited block passesbash -n.After this merges to master, re-run PR #2857's CI —
pull_requestruns use the base branch's workflow definition, so it will pick up the fixed guard and go green.Touches a CI workflow → human review per AGENTS.md §7.4.