Upgrade to wasmtime 48; polymorph-test 0.3.1 - #65
Merged
Conversation
wasmtime / wasmtime-wasi 47 -> 48. The polymorph-test pin moves to the v0.3.1 release (3631d4a1), which sits on wasmtime 48 -- the runner drives a wasmtime Store, so the two bumps travel together: cargo rev + CI action refs, and the matching @jsr/polymorph__test 0.3.1 in the polyengine tree (pnpm + deno lockfiles). wit-bindgen follows transitively to 0.61. Source follow-through: wasmtime-wasi 48 defaults AllowedNetworkUses to all-off where 47 allowed TCP/UDP; the composed conformance leg now grants allow_tcp so the in-guest provider can dial wasi:sockets. Without it 46/57 composed cases fail with AccessDenied. Verified: just check, runner-js-pin-check, exam-polyengine, polyengine-module-check, conformance-ct run-wasmtime + run-composed (57/57 each), demo::test.
lannbot
enabled auto-merge
September 7, 2026 03:48
lannbot
pushed a commit
that referenced
this pull request
Sep 7, 2026
The host module API and its @polyengine/protocol constraint (^0.3.1) are unchanged, so this is a patch under the caret-honest scheme; it carries the Rust host crate's move to wasmtime 48 (#65), so a release tag exists for consumers that link wasmtime-websocket alongside the other wasmtime-48 siblings.
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. The polymorph-test pin moves to the
v0.3.1 release (3631d4a1), which sits on wasmtime 48 -- the runner
drives a wasmtime Store, so the two bumps travel together: cargo rev +
CI action refs, and the matching @jsr/polymorph__test 0.3.1 in the
polyengine tree (pnpm + deno lockfiles). wit-bindgen follows
transitively to 0.61.
Source follow-through: wasmtime-wasi 48 defaults AllowedNetworkUses to
all-off where 47 allowed TCP/UDP; the composed conformance leg now
grants allow_tcp so the in-guest provider can dial wasi:sockets.
Without it 46/57 composed cases fail with AccessDenied.
Verified: just check, runner-js-pin-check, exam-polyengine,
polyengine-module-check, conformance-ct run-wasmtime + run-composed
(57/57 each), demo::test.
Automerge armed (merge commit).