ci: auto-open release/vX.Y on a new minor/major line#18
Merged
Conversation
After publishing, if master cut a new line (vX.Y.0), fork release/vX.Y at the same lock commit so back-ports have a home. Patches (Z>0) and flavor builds don't open a line; existing branches are left alone. Safe because the branch-creation push is ignored by the detect guard (no spurious release). Also re-applies the versions.env comment fix that was dropped when #17 merged, and updates the README back-patch section (auto-creation + name-based scoping). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
julian-goldstein
removed this pull request from the merge queue due to a manual request
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
1 participant
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.
What
After a publish on
master, if it cut a new line (vX.Y.0), CI forksrelease/vX.Yat the same lock commit — so a back-port always has a branch to land on. Patches (vX.Y.Z, Z>0) and flavor builds don't open a line; existing branches are untouched.This is only safe because of the earlier branch-creation guard — the auto-created branch's creation push is ignored by
detect, so it can't cut a spurious release.Also in this PR
versions.envcomment fix that was dropped when ci: no publish on branch creation / empty commit range #17 merged (master still said "bumps it by 0.1").Self-demonstrating
Merging this cuts
v0.8.0(unmarked → minor) and the new step then auto-opensrelease/v0.8.