-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build releases using GoReleaser
#375
Conversation
Codecov Report
@@ Coverage Diff @@
## master #375 +/- ##
=======================================
Coverage 69.72% 69.72%
=======================================
Files 33 33
Lines 1559 1559
=======================================
Hits 1087 1087
Misses 439 439
Partials 33 33 Continue to review full report at Codecov.
|
Fix |
e52c8de
to
1ff560e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be neat to see how UPX
fits into this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jmatias : Please remove the schema json from the PR.
@jmatias : At this point, the only thing preventing approval/merge is the increased binary size on non arm machines. Talisman build scripts used UPX to make the binary as small as can be. |
Regardless of GoReleaser, the issue would still be there for ARM (though they are working on it, we could try building the source code from their main branch) That being said, 8 MB nowadays does not feel like a whole lot — I would argue that it's acceptable for now until we find a way to either tap into the build hooks or do it post release. (And by that I mean just doing an empty release and then writing something ourselves that uploads the binaries). I vote for keeping the 8 MB binaries for now. |
No description provided.