ci(release): tag automatically when a dev-v* branch merges to main - #297
Merged
Conversation
Delegates to the reusable workflow in fleetbase/fleetbase, which validates and pushes the tag; create-release.yml and the publish jobs here already chain off the tag push. The version is never retyped — it comes from the dev-v* branch name, and the tag is refused unless the version files and RELEASE.md already agree with it. This repository is an ember addon plus a server, so it carries composer.json, package.json and extension.json. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #297 +/- ##
===========================================
Coverage 100.00% 100.00%
Complexity 9766 9766
===========================================
Files 521 521
Lines 37762 37762
===========================================
Hits 37762 37762
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Matches fleetbase/fleetbase, which has always used body_path. The release workflow now requires RELEASE.md and refuses to tag without it, so without this the notes would be mandatory to write and displayed nowhere. generate_release_notes stays on so GitHub's commit list is appended beneath the hand-written notes.
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.
Adds the release-tag caller. Part of the rollout for fleetbase/fleetbase#620, which holds the reusable workflow this delegates to.
What it does
When a
dev-v*branch is merged to main, it validates and pushes the tag — and nothing else.create-release.ymland the publish jobs in this repository already chain offpush: tags: ['v*'], so a second release path would duplicate them.The version is never retyped. It comes from the branch name (
dev-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
dev-v<semver>branchRELEASE.mdexists, is non-empty, and its first line names this versionThe tag goes on the PR's merge commit, never on
mainat run time.Before this can release
@mainwill not resolve until it does.RELEASE.mdwhose first line names the version, e.g.🤖 Generated with Claude Code