Create a new release on every pull request merge #1
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.
Using semantic versioning[1]
Use GoReleaser[2] to create a new release every time a pull request is
merged to master.
This requires each pull request to have a semantic version label, which
we enforce by using a label-checker GitHub Action[3].
[1] https://semver.org/
[2] https://goreleaser.com/ci/
[3] https://github.com/agilepathway/label-checker
NB we don't build an executable when releasing, as this is not
(currently, anyway) a Go project.