Repository navigation
update to Wasmtime 50 - #283
Merged
Merged
Conversation
rvolosatovs
force-pushed
the
roman/deps/wasmtime-50
branch
from
October 23, 2026 14:15
3646125 to
971203a
Compare
rvolosatovs
marked this pull request as ready for review
October 23, 2026 14:17
rvolosatovs
force-pushed
the
roman/deps/wasmtime-50
branch
from
October 24, 2026 08:44
805237d to
77f1c5b
Compare
SpaceManiac
approved these changes
Oct 26, 2026
Move `wasmtime`, `wasmtime-wizer` and `cranelift-codegen` to Wasmtime 50, together with: - the wRPC 0.18.0 release crates from crates.io (`wit-bindgen-wrpc` 0.12, `wrpc-http` 0.1, `wrpc-transport` 0.30, `wrpc-wave` 0.1) instead of git pins, which are on Wasmtime 50 and `wasm-tokio` 0.8; - Nightstream at the LFDT-Nightstream/Nightstream#184 merge commit (7db6b98d), which moves `neo-wasm` to Wasmtime 50; - the wasm-tools crates and `wasm-wave` 0.261, which Wasmtime 50 uses; - the toolchain and MSRV 1.97.0, which Wasmtime 50 requires. API changes followed: - `wit_component::encode` takes a `canonical_names` flag; - `wasmparser` module section ranges and the `wasmprinter` custom section offset are `u64`, so `TemplateBuildError::InvalidCoreModuleRange` now carries a `Range<u64>`; - `neo_wasm::extract_wasm_program_artifacts` returns `WasmProgramError`, surfaced as the new `TemplateBuildError::ProgramExtraction`. Also fix the clippy lints new in Rust 1.97 in `starstream-to-wasm`. `wasmprinter` now prints import signatures inline, hence the codegen snapshot churn. Breaking: `TemplateBuildError` gains `ProgramExtraction`, and `InvalidCoreModuleRange` carries a `Range<u64>`. Assisted-by: anthropic:claude-opus-5-5 Signed-off-by: Roman Volosatovs <rvolosatovs@riseup.net>
rvolosatovs
force-pushed
the
roman/deps/wasmtime-50
branch
from
October 26, 2026 11:06
77f1c5b to
f9108ac
Compare
rvolosatovs
enabled auto-merge (squash)
October 26, 2026 11:07
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.
Moves Starstream to Wasmtime 50, and with it:
(
wit-bindgen-wrpc0.12,wrpc-http0.1,wrpc-transport0.30,wrpc-wave0.1) replace the gitpins.
(wasm) update wasmtime to 50 Nightstream#184 merge commit (7db6b98d),
which moves
neo-wasmto Wasmtime 50.wasm-wavego to 0.261, the versionsWasmtime 50 uses.
requires.
Code changes the new dependency versions required:
wit_component::encodetakes a newcanonical_namesflag; we pass
false.wasmparsermodule section ranges and thewasmprintercustom-section offset are now
u64.TemplateBuildError::InvalidCoreModuleRangenow carries aRange<u64>.neo_wasm::extract_wasm_program_artifactsnow returnsWasmProgramError, surfaced as a newTemplateBuildError::ProgramExtractionvariant.(wasm) update wasmtime to 50 Nightstream#184 is based on a newer
Nightstream main than our previous pin, so this pulls in
25 upstream commits.
starstream-to-wasm.The codegen snapshot churn is all
wasmprinternowprinting import signatures inline.
Breaking:
TemplateBuildErrorinstarstream-proving-runtimegains aProgramExtractionvariant, and
InvalidCoreModuleRangechanges its payloadtype.
The wRPC release predates bytecodealliance/wrpc@ada1e297,
so
wrpc-transportonce again pullswasi0.14 on wasmtargets.