ci(release): gate hotfix pull requests into main (CLI-2442) - #6929
Draft
kanadgupta wants to merge 1 commit into
Draft
kanadgupta wants to merge 1 commit into
kanadgupta wants to merge 1 commit into
Conversation
Hotfix PRs into main now get the full Test suite, an always-reporting deploy-check that enforces a patch-type title on hotfix/* heads, and an automatic dry-run build-and-smoke rehearsal. The scheduled develop promotion skips Test and passes deploy-check so its head SHA carries a success for the release App's direct push. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This branch has not been deployed
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.
First of three PRs for the CLI hotfix release process. A hotfix is a
hotfix/*PR intomainwith afix,perf, orreverttitle; squash-merging publishes the next stable patch through the unchanged pipeline. This PR adds the gating that such a PR gets automatically.main. Every job skips when the PR is the scheduleddeveloppromotion, whose head already passed the merge queue. Therun-ciwrapper no longer treats ready PRs intomainas stacked, so nothing double-runs.developpromotion it succeeds. Onhotfix/*heads it requires the title to start withfix,perf, orrevert, with an optional scope and no!, and the failure message says what to change. Any other head fails. The job is named so it can become a required status check onmainonce this is promoted; the success on the promotion's head SHA is what the release App's direct push will satisfy.mainand runs the shared release pipeline withdry_run: true, restoring the build-and-smoke rehearsal that beta normally provides. Dispatch inputs keep their defaults. Runs are per-PR concurrent with cancel-in-progress.Stays in draft until the release App holds its
developruleset bypass, which the back-merge PR depends on. The runbook and ADR follow in the docs PR.🤖 Generated with Claude Code