ci(release): adopt the release/v* branch convention - #170
Open
roncodes wants to merge 1 commit into
Open
Conversation
Both prefixes are honoured so a release branch opened before the rename still releases. A merge that produces no tag and no publish looks exactly like a successful one, so the cutover is deliberately not a flag day.
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.
Adopts the
release/v0.0.0branch convention. Companion to fleetbase/fleetbase#641, which holds the reusable workflow this delegates to.What changed
One line, so the caller matches either prefix:
Why both, rather than a cutover
A hard switch would leave any release branch already open unrecognised — and a merge that produces no tag and no publish looks exactly like a successful one.
dev-v*keeps working; drop that arm once no such branch remains open.Merge order
fleetbase/fleetbase#641 first. This caller references the reusable workflow at
@main, sorelease/v*only starts being accepted once that lands. Merging this one early is harmless — it just keeps behaving as it does today.🤖 Generated with Claude Code