ci: introduced goreleaser#24
Merged
Merged
Conversation
This PR proposes to use the goreleaser tool to automate releases. It builds a github release with binary artifacts and notes. * .goreleaser config with multi-platform binary builds, binary compaction (upx) and release notes produced by the github API * CI workflow that runs goreleaser on push tag events Signed-off-by: Frédéric BIDON <fredbi@yahoo.com>
Pull Request Test Coverage Report for Build 19612212583Details
💛 - Coveralls |
Ma11hewThomas
approved these changes
Nov 23, 2025
Closed
Contributor
|
Thanks! |
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
3 participants
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.
This PR proposes to use the goreleaser tool to automate releases.
It builds a github release with binary artifacts and notes.
I've been able to test the process on my fork, including the final step (changelog using API, create release in github).
The workflow created a release that looks like this on my fork: https://github.com/fredbi/go-ctrf-json-reporter/releases
You might want to adapt the naming conventions for the archives. These are just the (sensible) defaults from goreleaser.
The changelog is obtained from github API and is not great. You might want to improve this at some point.
Note: on my fork, since it is the first release, the changelog captures the full history.