feat(p3): retarget WASI P3 WIT to stable v0.3.0 (#500) - #506
Merged
Conversation
WASI 0.3.0 was ratified 2026-06-11. The stable tag renamed the WIT location from proposals/<name>/wit-0.3.0-draft/ (RC) to proposals/<name>/wit/, so the RC-pinned wasi_p3_deps.bzl no longer matched. Retarget wasi_p3_deps.bzl from the RC monorepo tag (v0.3.0-rc-2026-03-15) to the stable v0.3.0 tag: new glob paths (proposals/<name>/wit/), strip_prefix WASI-0.3.0, and archive sha256 619928e4754a14db106ae42318daa5c7e29b842ab884662d6d86d8d1ac9a76fd. Enable the WASI P3 WIT in this repo's own build (wasi_wit init include_p3 = True + use_repo wasi_p3) — affects only this repo's CI; downstream consumers opt in separately — and add //test/p3:wasi_p3_wit_build_test so the stable WIT (cli/http/clocks/filesystem/sockets/random, with cross-package deps) stays green. Verified: bazel test //test/p3:wasi_p3_wit_build_test PASSES (fetches v0.3.0, parses all six interface wit_library targets). First chunk of #500. Remaining: wasmtime 43->45 + wit-bindgen 0.58 checksums, graduate the experimental-p3 bundle, land the dual-compile work. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
First chunk of #500 (WASI P3 RC→stable retarget). WASI 0.3.0 was ratified 2026-06-11.
Problem
The stable v0.3.0 tag renamed the WIT location from
proposals/<name>/wit-0.3.0-draft/(RC) toproposals/<name>/wit/.wasi_p3_deps.bzlwas pinned to the RC monorepo tag (v0.3.0-rc-2026-03-15) with the old glob paths, so it no longer matched the ratified spec.Change
wasi_p3_deps.bzl→ stablev0.3.0: globproposals/<name>/wit/*.wit,strip_prefix = WASI-0.3.0, sha256619928e4754a14db106ae42318daa5c7e29b842ab884662d6d86d8d1ac9a76fd.MODULE.bazel→wasi_wit.init(include_p3 = True)+use_repo(..., "wasi_p3"). This enables the P3 WASI WIT in this repo's own CI only; downstream consumers still opt in via their owninclude_p3 = True.test/p3/BUILD.bazel→ newwasi_p3_wit_build_testcovering all six interface targets (cli/http/clocks/filesystem/sockets/random), so the retarget can't silently rot. (The existingp3_build_testonly exercises the rustwasi_version=p3rule path with a custom WIT — not these WASI interfaces.)Verification
✅
bazel test //test/p3:wasi_p3_wit_build_testPASSES — fetches v0.3.0 and parses all six wit_library targets with cross-package deps.Remaining #500 chunks (follow-up PRs)
43.0.1→45.x+ wit-bindgen0.55→0.58checksums (P3 toolchain bump).experimental-p3bundle; updatecompatibility.wasi_rc→ final.fix/p3-dual-compilework; re-verifyexamples/p3/*.🤖 Generated with Claude Code