-
Notifications
You must be signed in to change notification settings - Fork 12
Merge wasmer v6.1.0 #29
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
Open
bragaigor
wants to merge
1,855
commits into
stylus
Choose a base branch
from
merge-wasmer-v6.1.0
base: stylus
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
Implement Memory::size function
feat: support sys-minimal feature for WASIX, allowing users to selectively enable features they need when running natively
…pinner-during-module-compilation feat(cli): Add loading spinner when compiling modules in TTY
…h-threads Linker: fix dlsym'ing functions from the main modules when there are …
Browser driven login can sometimes fail, so we provide fallback instructions for manual login.
Make table methods don’t fail in the browser
Fix/eh nested catch ref
Allow -u instead of --unpack. For convenience...
…mand-allow-u-shortform-for-unpack chore(cli): package unpack command: add shortform -u
Clean up the wasmer-sdk crate * Set version (should not track the main runtime version) * Add some docs * Move package publishing to submodule * Rename PublishError to PackagePublishError * Run expensive operations on blocking threads
Let consumers of the crate pick the features instead.
Use custom error type instead of anyhow::Error
For forwards compat.
* Templates that do not have a wasmer.toml (remote build templates) now auto-create a basic app.yaml file, and no longer go into a prompt loop * When deploying a directory with app.yaml but no wasmer.toml, the user is now prompted to do a remote build instead. If not approved, the deployment will fail.
* For remote builds, only gitignore is taken into account. * For all other builds, only wasmerignore is taken into account.
fix(cli): Improve behaviour for deployments without wasmer.toml
Use wasmerignore for bundling and gitignore for remote builds
Release 6.1.0
Signed-off-by: Igor Braga <5835477+bragaigor@users.noreply.github.com>
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.
Merge wasmer v6.1.0