Repository navigation
feat: route bugfix carve-out releases through a PR like normal releases (#2851) - #2853
Conversation
📦 Built Package ArtifactBranch: Option A — Install this exact build (recommended)npm install -g billion-context@0.0.3167-pr.2853.57e3811This exact version is immutable and reproducible. The rolling Option B — Download artifact
tar xzf billion-context-pr2853.tgz
npm install -g packageInstall instructions are refreshed on each push. |
Review 结论:可合(人工门禁) — 单 commit
合并前建议:先 rebase 到当前 master —— PR 落后 6 个提交(全是无关的 src perf/diag:#2829/#2828/#2827/#2824×3),与这 3 个文件零重叠,rebase 会干净,属线性历史卫生而非正确性必需。 门禁:触及 CI 发布基础设施 → §7.4 强制人工评审,不可 auto-merge;由你手动合并 PR 链接:#2853 。合并后即可按你计划切第二个 PR( |
…es (#2851) The old channel auto-published on push of a bugfix-release/** branch, with no human review gate. Now the carve-out branch goes through a PR against master; release-bugfix.yml fires when that PR is MERGED and publishes the PRE-MERGE PR-head tree (last tag + fix + version bump), strictly excluding master's other unreleased work. All fail-closed guards, the pre-flight and full-CI gates are unchanged; manual workflow_dispatch on an explicitly chosen ref remains the emergency fallback. Pushing a bugfix-release/** branch triggers nothing anymore.
98ac339 to
810e081
Compare
📦 Merged Build PublishedThis merge to master was published as npm install -g billion-context@0.0.302-master.649a289 # this exact build
npm install -g billion-context@master # always the newest merged build
|
ranxianglei#2853 made the carve-out channel PR-gated with bugfix-release/* as the marker prefix, but ci.yml version-guard still only whitelisted *_release-v*. Every carve-out release PR (e.g. ranxianglei#2857) went red, and release-bugfix.yml's fail-closed full-CI gate then blocked the merge-time publish.
What
Per #2851 (owner request): the bugfix carve-out channel must go through a PR like normal releases instead of silently publishing on branch push. The ONLY difference from a normal release stays exactly what it always was: the published tree is the carve-out PR itself (+ version bump), never the post-merge master.
Changes
release-bugfix.yml:push: branches: ['bugfix-release/**']→pull_request: types: [closed], branches: [master]. Pushing abugfix-release/**branch now triggers NOTHING.resolve: reads the event payload — publishes only when the closed PR was merged, its head branch matchesbugfix-release/*, and head/base are the same repo (fork PRs fail loudly). Non-matching closes print a notice and skip (green).fetch-depth: 0), the job switches to the pre-merge PR head sha (git checkout --detach) and exportsGITHUB_SHA=<head sha>/GITHUB_REF_NAME=<branch>into both CI-gate steps — so the full-CI gate reuses the lane runs the PR itself already produced at that exact sha (the path-filteredpull_requesttriggers on every required lane), and dispatches only what is missing.npm ci+ typecheck + test + build,ACP_TEST_CLAUDE_NATIVE=1tests/claude-native.test.ts linux live-E2E subtests fail/hang in shared multi-agent sandboxes #1248), full-CI gate, prerelease tag logic, tag creation,npm publish, GitHub Release notes fromgit log LAST..HEAD.workflow_dispatchkept as the manual emergency fallback (human picks the ref in the Actions UI; every guard still runs).Docs:
reference/release.md(Bugfix carve-out channel section rewritten to the PR-gated process) andAGENTS.md§5 bullet updated to match.Behavior change disclosure (old → new)
bugfix-release/v…branch (or manual dispatch)workflow_dispatchon an explicit refThe
bugfix-release/prefix remains the carve-out MARKER:release.yml's detection (date-prefixed_release-vpattern) deliberately does not match it, so merging the PR cannot double-publish the post-merge master through the normal channel.Notes
bugfix-release/v0.1.195-dsh-compaction-422= v0.1.194 + fix: refuse dsh native compaction with 422, not auth-class 403 (#2843) #2844 fix + version bump as the second PR, which closes bugfix通道也走pr而不是静默推分支 #2851.Part of #2851 (second PR closes it).