Rename release pipeline commit messages and PR title from chore to release - #241
Merged
Conversation
…lease Replace the conventional-commit type "chore" with "release" for commit messages and "Finalization PR:" for the PR title, as "chore" implies routine maintenance rather than a release finalization. - Commit 1: "chore: release version X" -> "release: set version X" - Commit 2: "chore: prepare next version Y" -> "release: prepare next version Y" - PR title: "chore: release X and prepare Y" -> "Finalization PR: release X and prepare Y" Branch name "release/vX.Y.Z" is unchanged. Generated with [Devin](https://devin.ai) Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Rename release pipeline commit messages and PR title from chore to release
Problem
The release workflow used the conventional-commit type
chorefor its automated commits and PR title.choreimplies routine maintenance (e.g., dependency bumps, formatting), which is misleading for a release finalization — both in the git history and in the PR review queue.Changes
.github/workflows/maven-central-release.yml(only changed file)chore: release version $VERSIONrelease: set version $VERSIONchore: prepare next version $NEXT_VERSIONrelease: prepare next version $NEXT_VERSIONchore: release $VERSION and prepare $NEXT_VERSIONFinalization PR: release $VERSION and prepare $NEXT_VERSIONrelease/v$VERSIONrelease/v$VERSION(unchanged)Release $VERSIONRelease $VERSION(unchanged)Rationale
release:is the appropriate conventional-commit type for version bumps and release preparationFinalization PR:makes the PR immediately recognizable in the review queue as the final step of a releaserelease/v$VERSIONis already clear and was not changedVerification