jrandolf opened PR #14800 from jrandolf:wasi-0.3.2 to bytecodealliance:main:
This updates the vendored WASIp3 WITs to the 0.3.2 release of WASI, so
wasmtime-wasiandwasmtime-wasi-httpnow implement the 0.3.2 versions of the interfaces. Apart from version numbers the WITs are the same as 0.3.0; the only other difference is a doc comment about casing inwasi:http'sfields.Components built against 0.3.0, which includes everything Rust's
wasm32-wasip3target produces today, keep working because imports and exports are matched on semver-compatible versions. I've added a CLI test that runs the existing p3 WAT test at@0.3.0against the new host to make sure that stays true.
jrandolf requested rvolosatovs for a review on PR #14800.
jrandolf requested wasmtime-wasi-reviewers for a review on PR #14800.
jrandolf requested dicej for a review on PR #14800.
jrandolf requested wasmtime-core-reviewers for a review on PR #14800.
jrandolf requested fitzgen for a review on PR #14800.
jrandolf requested wasmtime-default-reviewers for a review on PR #14800.
github-actions[bot] added the label wasi on PR #14800.
alexcrichton commented on PR #14800:
I'll note that given how WASI versioning works we cannot land this yet. WASI 0.3.1 requires
map<K, V>and the(implements ...)features to be supported, and neither is on-by-default right now. Notablyimplementshas no fuzzing andmaphas been fuzzed for a bit and might be ready. I see sibling PRs for these, however.
rvolosatovs removed the review request for rvolosatovs from PR #14800.
fitzgen removed the review request for fitzgen from PR #14800.
jrandolf updated PR #14800.
Last updated: Oct 31 2026 at 23:03 UTC