ci: cut releases on demand instead of on every merge to main - #135
Merged
Merged
Conversation
A merge to main now runs build-test and stops. The release and publish jobs run only on a manual workflow_dispatch, so fixes can land on main in small branches and accumulate until a release is wanted. semantic-release already reads every commit since the last tag, so one run cuts one version at the highest bump those commits call for, with a combined changelog. The release job also joins publish on the protected release environment. Dispatch is available to anyone with write access, and without the gate such a run would consume a version number and cut a tag, a GitHub release and a changelog entry before any approval, leaving that version unusable.
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.
A merge to main now runs build-test and stops. The release and publish jobs run only on a manual workflow_dispatch, so fixes can land on main in small branches and accumulate until a release is wanted. semantic-release already reads every commit since the last tag, so one run cuts one version at the highest bump those commits call for, with a combined changelog.
The release job also joins publish on the protected release environment. Dispatch is available to anyone with write access, and without the gate such a run would consume a version number and cut a tag, a GitHub release and a changelog entry before any approval, leaving that version unusable.