ci: auto-incrementing release workflow - #12
Merged
Conversation
On every push to main, compute the next semver tag from the latest existing tag and cut a GitHub release. Patch bump by default; "#minor"/"#major" in the commit message bump those instead, and "[skip release]" skips.
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
.github/workflows/release.yml: on every push tomain, compute the nextsemver tag from the latest existing tag and cut a GitHub release (with generated
notes) pointing at the merged commit.
#minoror#majorin the (squash)commit message to bump those.
[skip release]skips.gh release create(GitHub API), so it's authored by theActions bot — no tagger email-privacy issues.
concurrency: releaseserializes runs; tag creation doesn't push tomain,so there's no trigger loop.
Note: merging this PR will itself produce the next release (
v0.12.1) unless thesquash message includes
[skip release]. v2+ majors would need the/vNmodulepath change in go.mod — only relevant if you ever
#majorpast v1.