Skip to content

Update WASIp2 bindings to 0.2.12, use exit-with-code - #860

Merged
alexcrichton merged 3 commits into
WebAssembly:mainfrom
alexcrichton:update-wasip23
Aug 7, 2026
Merged

alexcrichton merged 3 commits into
WebAssembly:mainfrom
alexcrichton:update-wasip23

Conversation

@alexcrichton

Copy link
Copy Markdown
Collaborator

So far wasi-libc has never updated its wasip2 bindings, and I feel it's about time this is done. This is used to get access to exit-with-code. Users needing to use the older version of WASIp2 can continue to use historical versions of wasi-libc/wasi-sdk, much the same as needing to use an older LLVM version.

@alexcrichton
alexcrichton marked this pull request as ready for review August 3, 2026 14:40
@alexcrichton
alexcrichton requested a review from dicej August 3, 2026 14:41
@alexcrichton
alexcrichton merged commit 8d8348e into WebAssembly:main Aug 7, 2026
36 checks passed
@alexcrichton
alexcrichton deleted the update-wasip23 branch August 7, 2026 17:10
krig added a commit to GramEditor/gram that referenced this pull request Nov 14, 2026
… (#737)

Still not entirely clear on _why_ this breaks, but my theory is that
when compiling Wasm extensions now, the extensions end up using WASI
0.2.12 instead of 0.2.0, which adds exit-with-code, and the older
wasmtime loader couldn't handle it.

See WebAssembly/wasi-libc#860

Upgrading wasmtime to 48.0.8 seems to solve the issue at least.

Ended up upgrading a bunch of other things as well. The most
recent tree-sitter release (0.27.2) is built with 48.0.8 so that
was the most recent version that could be upgraded to.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants