Skip to content

ci(release): adopt the release/v* branch convention - #36

Merged
roncodes merged 1 commit into
mainfrom
ci/release-branch-naming
Sep 8, 2026
Merged

ci(release): adopt the release/v* branch convention#36
roncodes merged 1 commit into
mainfrom
ci/release-branch-naming

Conversation

@roncodes

@roncodes roncodes commented Sep 3, 2026

Copy link
Copy Markdown
Member

Adopts the release/v0.0.0 branch convention. Companion to fleetbase/fleetbase#641, which holds the reusable workflow this delegates to.

What changed

One line, so the caller matches either prefix:

if: github.event_name == 'workflow_dispatch' ||
    (github.event.pull_request.merged == true &&
     (startsWith(github.event.pull_request.head.ref, 'release/v') ||
      startsWith(github.event.pull_request.head.ref, 'dev-v')))

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, so release/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

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.
@roncodes
roncodes merged commit 46a2688 into main Sep 8, 2026
6 of 7 checks passed
@roncodes
roncodes deleted the ci/release-branch-naming branch September 8, 2026 03:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant