feat(p3): bump default runtime to wasmtime 45 (#500) - #509
Merged
Conversation
) WASI 0.3.0 was ratified 2026-06-11. wasmtime 45 runs it; wit-bindgen 0.58 emits the stable async codegen. Bump the active default toolchain (P3 shares the same tools as P2, per the wasi_version=target-property design) from wasmtime 43.0.1 / wit-bindgen 0.55.0 to wasmtime 45.0.1 / wit-bindgen 0.58.0, in: - MODULE.bazel (wasmtime toolchain version) - tool_versions.bzl TOOL_VERSIONS + P3_TOOL_VERSIONS + compatibility matrix Registry entries for both were added in #508. Verified locally (the bump is global, so both paths checked): - //examples/basic:hello_component (P2) builds. - //test/p3:all (p2_build_test, p3_build_test, wasi_p3_wit_build_test) all pass. The wit-bindgen binary 0.58 / crate skew did not break the rust P3 async path. CI runs the full example/test suite for the comprehensive gate. Chunk 2b of #500. Remaining: graduate the experimental-p3 bundle; land fix/p3-dual-compile. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
CI showed wit-bindgen 0.58 changes the C/C++ codegen type names (data_structures_world_list_node_id_t etc.), breaking the hand-written examples/cpp_component/data_structures source. Since wasmtime 45 (the WASI 0.3.0-stable runtime) is the actual need and wit-bindgen 0.55 already builds the rust P3 path, keep wit-bindgen at 0.55 here and defer the 0.58 bump (which requires adapting the C/C++ examples to the new codegen) to a follow-up. Verified locally: //examples/cpp_component/data_structures:all builds (the case that failed CI), and //test/p3:all (p2/p3/wasi_p3_wit) all pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
avrabe
changed the title
6 tasks
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
1 participant
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.
#500 chunk 2b (revised). WASI 0.3.0 was ratified 2026-06-11; wasmtime 45 runs it.
Bumps the default runtime to wasmtime 45.0.1 (MODULE.bazel +
tool_versions.bzlTOOL_VERSIONS/P3_TOOL_VERSIONS + compat matrix). Registry entry added in #508.wit-bindgen held at 0.55 (not 0.58): CI showed wit-bindgen 0.58 changes the C/C++ codegen type names, breaking
examples/cpp_component/data_structures. wit-bindgen 0.55 already builds the rust P3 path, so the runtime bump is decoupled from the codegen bump.Verification (local)
//examples/cpp_component/data_structures:allbuilds (the target that failed CI on 0.58)//examples/basic:hello_component(P2) builds//test/p3:all— p2/p3/wasi_p3_wit all passFollow-ups (#500)
experimental-p3bundle; landfix/p3-dual-compile.🤖 Generated with Claude Code