add arm64 to goreleaser builds #47
Merged
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
😄 Yeah, I think this should be fine. If it's okay, I'm thinking to address #44 before cutting a new release. |
|
Absolutely fine by me ;) |
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.
Hi and thank you very much for this project!
We are currently migrating some of our instances to ARM-based builds and
calertis one of the few things keeping us from doing so for our monitoring stack.I have only tested building locally on macOS with
goreleaser build --snapshotso far, but currently lack the resources to test this any further. I am, however, fairly confident that this should "just work" (famous last words, I know).I also didn't extend the
dockerssection because I didn't want to introduce a tag naming scheme, etc.