Upgrade the wasmtime host to wasmtime 48 - #18
Merged
Merged
Conversation
The rest of the family moved to wasmtime 48 today; this is the last host crate on 47. No API change reached this crate: the store grants no network, so wasmtime-wasi 48's all-off AllowedNetworkUses default is moot here. Lock: the wasmtime family plus cranelift 0.135 and the wasm-tools 0.254 line; nothing else.
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
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 rest of the family moved to wasmtime 48 today; this was the last host crate on 47. No source change: the store grants no network, so wasmtime-wasi 48's all-off
AllowedNetworkUsesdefault is moot here. Lock: the wasmtime family plus cranelift 0.135 and the wasm-tools 0.254 line viacargo update -p wasmtime -p wasmtime-wasi; nothing else.Gates run locally: host clippy
-D warnings,just host-component, hostcargo test(5/5).Automerge armed.