Repository navigation
ci: release by itself on every merge to main that carries a feat, fix or perf commit - #14
Merged
Merged
Conversation
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.
Until now a release needed someone to push a tag by hand, and v0.3.1 was already 6 commits behind
main.On every push to
mainthe release workflow now: runs gofmt, vet and tests; computes the next version from the conventional commits since the last tag (feat:minor,fix:/perf:/revert:patch,!orBREAKING CHANGE:minor before 1.0.0 and major after); pushes the tag; runs goreleaser (binaries andchecksums.txt).docs:,chore:,test:,ci:,refactor:alone release nothing. A tag pushed by hand still works. CONTRIBUTING documents it.A tag pushed with the workflow token does not start another workflow, so tagging and goreleaser run in the same job.
Checked locally on the real history without tagging anything: this repo would become v0.3.2; synthetic histories give no release for
docs:/chore:, a patch forfix:, a minor forfeat:andfeat!:(0.x).Merging this releases v0.3.2 right away, since
mainalready carries fixes since v0.3.1.