Use goreleaser to automatically build and publish binaries #64
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
Owner
|
Thank you, this was in my TODO. :) |
Contributor
Author
|
Since your |
Closed
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.
This PR will automatically build and publish binaries to the
Releasessection of your GitHub repo. To trigger a build after you finalize a new version you would still need to manually run something like:I have personally tested the built binaries on MacOS, Linux and Windows.
Here is the build process in my forked repo: https://github.com/jftuga/up/actions/runs/11850200632/job/33024746685
Here is what your release and binaries would look like: https://github.com/jftuga/up/releases
If this PR is accepted, I would then remove my forked repo, along with those releases / binaries to avoid any confusion.