Upgrade to wasmtime 48; sibling host crates to their wasmtime-48 commits - #105
Merged
Conversation
wasmtime / wasmtime-wasi 47 -> 48 in host-wasmtime, and the sibling host-crate pins move to the commits that made the same bump: polymorph-webcrypto 44325359 (PR #402), polymorph-websocket ec3ffa27 (PR #65), polymorph-webrtc-datachannels fe05ecfd (main). One wasmtime across the whole host build. Lockfile fallout: wasm-tools crates 0.252 -> 0.254; rtc/webrtc move off the lann/webrtc fork pin to 0.21.0-rc.2 (the datachannels crate's own unwinding of that pin). Source follow-through: - wasmtime-wasi 48 defaults AllowedNetworkUses to all-off where 47 allowed TCP/UDP; the store grants allow_udp for the direct-addr path. Without it the udp and interop-udp pairings fail with AccessDenied on socket creation. - rtc 0.21: SettingEngineBuilder::set_include_loopback_candidate is now the builder-style with_include_loopback_candidate. Verified: just check, just test, just matrix (13/13 pairings).
lannbot
enabled auto-merge
September 7, 2026 04:10
Merged
lannbot
pushed a commit
that referenced
this pull request
Sep 7, 2026
The host module API and its @PolyEngine constraints (runtime ^0.6.3, protocol ^0.3.1) are unchanged, so this is a patch under the caret-honest scheme. It carries the endpoint's move to upstream iroh 1.1.0 / noq 1.2.0 (#104) -- a new iroh_endpoint.wasm, paired with iroh-relay 1.1.0 -- and the native host's move to wasmtime 48 with the sibling host crates at their wasmtime-48 commits (#105).
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
2 participants
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.
wasmtime / wasmtime-wasi 47 -> 48 in host-wasmtime, and the sibling
host-crate pins move to the commits that made the same bump:
polymorph-webcrypto 44325359 (PR #402), polymorph-websocket ec3ffa27
(PR #65), polymorph-webrtc-datachannels fe05ecfd (main). One wasmtime
across the whole host build. Lockfile fallout: wasm-tools crates
0.252 -> 0.254; rtc/webrtc move off the lann/webrtc fork pin to
0.21.0-rc.2 (the datachannels crate's own unwinding of that pin).
Source follow-through:
allowed TCP/UDP; the store grants allow_udp for the direct-addr
path. Without it the udp and interop-udp pairings fail with
AccessDenied on socket creation.
now the builder-style with_include_loopback_candidate.
Verified: just check, just test, just matrix (13/13 pairings).
Automerge armed (merge commit).