Stream: wasi

Topic: PSA: WASI monorepo migration is now complete

view this post on Zulip Yosh Wuyts (Nov 26 2025 at 01:23):

Hey all, @Bailey Hayes and I have just finished the bulk of the migration to the WASI monorepo, and it is now up and running!

GitHub - WebAssembly/WASI: WebAssembly System Interface
WebAssembly System Interface. Contribute to WebAssembly/WASI development by creating an account on GitHub.

view this post on Zulip Yosh Wuyts (Nov 26 2025 at 01:24):

All existing proposals have been migrated, issues have been moved too, and outstanding PRs closed. All proposal champions will have received invites for the monorepo as well.

view this post on Zulip Yosh Wuyts (Nov 26 2025 at 01:25):

We're still putting the finishing touches on the repo, including setting up code owners and recreating CI. PRs for both have been filed, just not merged yet. I expect us to turn that around in the next day or so.

view this post on Zulip Yosh Wuyts (Nov 26 2025 at 01:28):

You can find all the phase 3 proposals listed under the proposals/ directory in the WASI repo.

WASI/proposals at main · WebAssembly/WASI
WebAssembly System Interface. Contribute to WebAssembly/WASI development by creating an account on GitHub.

view this post on Zulip Yosh Wuyts (Nov 26 2025 at 01:30):

Either way! - We got the bulk of the migration done today, and even managed to bring over the project history too!

view this post on Zulip Yosh Wuyts (Nov 26 2025 at 01:33):

Wanted to make sure to let y'all know. And we'll share an update here too once we have CI up as well.

view this post on Zulip Jacob Lifshay (Nov 26 2025 at 06:57):

as I mentioned here, the migration inadvertently closed a bunch of unrelated issues since they happen to share the issue numbers with issues from the original repos that a commit mentioned as closing.

Migrate proposals into the WASI monorepo by yoshuawuyts · Pull Request #826 · WebAssembly/WASI
This is the first step in bringing all the proposals into a single repository, AKA creating a WASI monorepo. This was done in a similar way to bytecodealliance/wasmtime#11815 using the git-filter-r...

view this post on Zulip Jacob Lifshay (Nov 26 2025 at 06:58):

e.g.: https://github.com/WebAssembly/WASI/issues/25#event-21166962479

System collation and system timezone data · Issue #25 · WebAssembly/WASI
(Maybe this is two separate issues?) It's common for runtimes (or apps) to have to bundle entire copies of collation tables, timezone data, etc with every app distributed. It adds a considerable am...

view this post on Zulip Jacob Lifshay (Nov 26 2025 at 06:59):

wait, maybe not that specific issue, but I remember seeing a bunch of others

view this post on Zulip Jacob Lifshay (Nov 26 2025 at 07:01):

here's a much better example: https://github.com/WebAssembly/WASI/issues/56#event-21166968177

Blockchain call extension · Issue #56 · WebAssembly/WASI
Most blockchain functions map well to WASI except for call/transact, which is an RPC augmented with the ability to transfer the platform's native token (e.g., Eth) from the caller to the callee. It...

view this post on Zulip Jacob Lifshay (Nov 26 2025 at 07:03):

that's marked closed by https://github.com/WebAssembly/WASI/commit/2f08b9c03709a0ad6eae0714e3b49e84411b64a9 which obviously has nothing to do with blockchain.

Document fields-get return value when the key is not present · WebAssembly/WASI@2f08b9c
Resolves #56

view this post on Zulip Yosh Wuyts (Nov 26 2025 at 13:26):

Jacob Lifshay said:

as I mentioned here, the migration inadvertently closed a bunch of unrelated issues since they happen to share the issue numbers with issues from the original repos that a commit mentioned as closing.

thanks for catching that; that's really unfortunate - I'll go through them now to try and restore them, starting with the issues you've linked!

view this post on Zulip Yosh Wuyts (Nov 26 2025 at 13:29):

I found three more that had been inadvertently closed:

WASI IPC module · Issue #49 · WebAssembly/WASI
Hey there, everyone! As I very briefly described in WebAssembly/wasi-sdk#33, WASI at the moment seems to be lacking support for IPC communication. I think that this feature is essential for some ap...
Considerations for WASI standardization phases · Issue #38 · WebAssembly/WASI
Wasm has a phase process that describes how proposed features progress toward standardization. The process is designed to make it clear how to add to the wasm standard, both in terms of who should ...
Sharp edges of the current capability system · Issue #16 · WebAssembly/WASI
So far it seems the most advanced practical capability system is Capsicum. I think it would be nice to correlate their API with WASI API just to avoid some potential mistakes (see e.g. fine grained...

view this post on Zulip Yosh Wuyts (Nov 26 2025 at 13:32):

I found these by filtering the issue list to just the closed issues and then ordering by "recently updated". I think that should be all of them!

WebAssembly/WASI
WebAssembly System Interface. Contribute to WebAssembly/WASI development by creating an account on GitHub.

view this post on Zulip Yosh Wuyts (Nov 26 2025 at 13:32):

Thanks @Jacob Lifshay!

view this post on Zulip Yosh Wuyts (Nov 26 2025 at 22:54):

CI just got merged as well; we now have it up for both the 0.2 and 0.3 specs!

view this post on Zulip Yosh Wuyts (Nov 26 2025 at 22:56):

(That was all @Bailey Hayes btw!)

Last updated: Dec 06 2025 at 06:05 UTC