Install wasmer binary from Github releases #1765
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
jonaprieto
force-pushed
the
wasmer-release-binary
branch
from
e99a1f5
to
8370eab
Compare
jonaprieto
force-pushed
the
wasmer-release-binary
branch
from
4865a66
to
8cf38b3
Compare
Merged
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.
The current Github action responsible for installing Wasmer fails from time to time, and it also is outdated, not following the new NodeJS 16 requirement by Github.
We could use https://github.com/jaxxstorm/action-install-gh-release instead, but unfortunately, it does not have the proper support to expose the binaries contained in an inner folder, as in the case with the Wasmer release. In the meantime, let's use my fork while I open PR to the main repository.