add goreleaser and RELEASE.md #68
Merged
+109
−3
Conversation
This file contains 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.
I ran into difficulties creating a quick CI/CD process (#43 (comment)). The inclusion of Goreleaser will help us to release faster until we have a full CI/CD pipeline.
The goreleaser configuration included in this PR is the same one that was used to create the v0.0.8 release.
The settings chosen match the pattern used in previous tagged releases and make the process repeatable for new project maintainers.
Future iterations on the release process should seek to remove the local tagging phase, replacing it with a Github workflow (or similar CI build steps). Goreleaser could be replaced entirely with Github workflows or be run from Github workflows.
Goreleaser also supports brew publishing, relating to #38