ci(release): tag automatically when a release branch merges - #13
Open
roncodes wants to merge 2 commits into
Open
ci(release): tag automatically when a release branch merges#13roncodes wants to merge 2 commits into
roncodes wants to merge 2 commits into
Conversation
Delegates to the reusable workflow in fleetbase/fleetbase, which validates and pushes the tag. Accepts release/v0.0.0 and the legacy dev-v0.0.0.
The release workflow refuses to tag unless RELEASE.md's first line names the version being released. Seeded so that check has something to validate; the placeholder markers block publishing the template itself.
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.
Adds release-tag automation to this repository, using the
release/v0.0.0branch convention. Companion to fleetbase/fleetbase#641, which holds the reusable workflow this delegates to.What it does
When a release branch is merged, it validates and pushes the tag — and nothing else. Whatever this repository already runs on
push: tags: v*does the publishing, so there is no second release path.The version is never retyped: it comes from the branch name (
release/v1.2.3⇒v1.2.3), and the tag is refused unless every version file andRELEASE.mdalready agree with it.Validation, each failing rather than warning
release/v<semver>branch (legacydev-v<semver>still accepted)RELEASE.mdexists, is non-empty, and its first line names this versionRELEASE_NOTES_PLACEHOLDERmarker remainsThe tag goes on the PR's merge commit, never on the default branch at run time.
Also in this PR
A seeded
RELEASE.md. The workflow refuses to release without notes whose first line names the version — that check is the only thing that can distinguish notes written for this release from the previous release's notes nobody replaced. Replace both placeholder markers before your first release, or the tag is refused.Merge order
fleetbase/fleetbase#641 first, since this references the reusable workflow at
@main.🤖 Generated with Claude Code