Skip to content

Upgrade to wasmtime 48; polymorph-test 0.3.1 - #402

Merged
lannbot merged 1 commit into
mainfrom
bump/wasmtime-48
Sep 7, 2026
Merged

Upgrade to wasmtime 48; polymorph-test 0.3.1#402
lannbot merged 1 commit into
mainfrom
bump/wasmtime-48

Conversation

@lannbot

@lannbot lannbot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

wasmtime / wasmtime-wasi 47 -> 48 in every host crate, and the wasmtime
CLI pin in scripts/setup.sh to 48.0.1 to match the embedded engine.

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 five npm trees and the polyengine
deno.json. wit-bindgen follows transitively to 0.61.

No source changes needed. Verified: just check, conformance-ct
run-wasmtime + run-composed (0 failures), demo::test-composed,
runner-js-pin-check, polyengine-pin-check.


Automerge armed (merge commit).

wasmtime / wasmtime-wasi 47 -> 48 in every host crate, and the wasmtime
CLI pin in scripts/setup.sh to 48.0.1 to match the embedded engine.

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 five npm trees and the polyengine
deno.json. wit-bindgen follows transitively to 0.61.

No source changes needed. Verified: just check, conformance-ct
run-wasmtime + run-composed (0 failures), demo::test-composed,
runner-js-pin-check, polyengine-pin-check.
@lannbot
lannbot enabled auto-merge September 7, 2026 03:48
@lannbot
lannbot merged commit 4432535 into main Sep 7, 2026
10 checks passed
@lannbot
lannbot deleted the bump/wasmtime-48 branch September 7, 2026 04:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants