Skip to content

Conversation

@yoshuawuyts
Copy link
Member

This PR moves the content of the legacy/ directory to a dedicated wasi-0.1 branch. This should make the WASI 0.1 archive easier to find and link to for those who want to, while keeping the main branch focused on the development of upcoming WASI versions. This should create a better experience overall for people who care exclusively about WASI 0.1.

While this PR only affects the WASI 0.1 archive, the plan is to repeat this once more with the introduction of WASI 0.3. Just like we're doing here, we would create a new branch labeled wasi-0.2 and then use that as the archive for the existing WASI 0.2 interfaces and definitions. And with the introduction of WASI 1.0, we would do this one last time.

I've also gone ahead and setup branch protection rules for the WASI 0.1 branch to ensure it cannot just be deleted or force pushed to. That way we're treating it as a long-lasting archive branch, and not just something that is at risk of accidental deletion. For WASI 0.2 and beyond specifically, this also puts us in a position where we can consider publishing additional point releases should there ever be a need to.

I've also gone ahead and searched for any links to the legacy/ directory on GitHub, but from what I can tell all references are either historical or are forks of this repository. In a follow-up PR I'd like to see whether we can re-format the README a little, and see if we can start listing historical WASI versions under a dedicated heading to make it easier to find at a glance.

Thanks!

@yoshuawuyts yoshuawuyts requested a review from a team as a code owner December 17, 2025 15:45
@yoshuawuyts yoshuawuyts added this pull request to the merge queue Dec 18, 2025
Merged via the queue into WebAssembly:main with commit ce149c9 Dec 18, 2025
1 check passed
@yoshuawuyts yoshuawuyts deleted the legacy branch December 18, 2025 22:47
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