Include WASI 0.2.6 WITs #3356
Draft
Include WASI 0.2.6 WITs #3356
Conversation
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
Signed-off-by: itowlson <[email protected]>
alexcrichton
approved these changes
Nov 19, 2025
fibonacci1729
approved these changes
Nov 19, 2025
Collaborator
|
I think it would make sense to do this for whatever target envs we have published. |
Collaborator
|
For current published envs we have remaining: Good news is that updating |
| @@ -1,6 +1,11 @@ | |||
| package wasi:clocks@0.2.0; | |||
Collaborator
There was a problem hiding this comment.
For consistency, can we name this folder wit/deps/[email protected]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This aligns the Spin 3.5 WITs with what we actually support. This is to address an issue where compilers (e.g. Rust with the
wasm32-wasip2target) may emit up-level imports that run fine on Spin but fail target world validation. The risk of regressions seems low because 1. backward compatible and 2. Spin never actually uses these WITs, it just provides whatever thewasicrate gives it. This is more about a correct reference that we can publish for validation and/or use for SDKs etc.We should figure out whether to retcon the Spin 3.4 WITs too.
Draft for feedback and discussion (and integration testing!).