Goreleaser config update #193
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
… instead of replacements google#190.
flwyd
approved these changes
Jul 7, 2025
Contributor
flwyd
left a comment
flwyd
left a comment
There was a problem hiding this comment.
Thanks for the change! I'm hoping to get a release going this week.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Update configuration and release workflow to use goreleaser in order to correctly cross compile binaries, due to backward incompatible changes/deprecations to their (goreleaser's) API since last release. See issue #190 for details.
For reference, observe the name output of the assets in a test release (on a fork of this repo). I believe I have replicated the output of the previous config, but let me know if there are any changes needed.