Skip to content
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

Update goreleaser to release statically linked binary #2559

Open
4 tasks
kaustubhkapatral opened this issue Jun 24, 2024 · 0 comments
Open
4 tasks

Update goreleaser to release statically linked binary #2559

kaustubhkapatral opened this issue Jun 24, 2024 · 0 comments

Comments

@kaustubhkapatral
Copy link

Summary

Add support in goreleaser to release statically linked binary when a new tag is pushed.

Problem Definition

As umee has cosmwasm integration in it, if a binary is built using the regular build instructions of make build or make install on one host, it can't be used to run on a different host before downloading the libwasm file on the new host. The same issue is present for the binary which gets released when a new tag is released. A separate set of instructions is always provided to the validators to make sure they update their libwasm file if they use pre-built binary. Ex:- the libwasmvm update section present under Validators header present here:- https://github.com/umee-network/umee/releases/tag/v6.4.0

Proposal

Update goreleaser to build and release statically linked binary that does not require any libwasmvm prerequisite setup.

For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant