Skip to content

docs: correct stale references, document WASI 0.3.1, expand contribute page - #63

Merged
ericgregory merged 3 commits into
bytecodealliance:mainfrom
ericgregory:ericgregory/refresh-release-info
Aug 26, 2026
Merged

docs: correct stale references, document WASI 0.3.1, expand contribute page#63
ericgregory merged 3 commits into
bytecodealliance:mainfrom
ericgregory:ericgregory/refresh-release-info

Conversation

@ericgregory

@ericgregory ericgregory commented Aug 26, 2026

Copy link
Copy Markdown
Collaborator

Corrects six broken links and the stale Wasmtime, WASI 0.2, and migration guide claims, syncs the proposal tables with upstream, and documents WASI 0.3.1. Also expands the contribute page, refreshes the 0.3 toolchain rows on the Languages page, and adds a steer between WASI 0.2 and 0.3 on the releases table.

Merge after #62.

Fixes six broken links: the Subgroup charter and the WASI contributing
guide moved or were referenced with the wrong case, the io proposal
directory no longer exists on main, the wasip2 README path is gone, and
WAMR moved to wamr.dev.

Corrects statements that the WASI 0.3.0 release made false: WASI 0.2 is
no longer the most recent stable release, Wasmtime 46 has shipped rather
than being forthcoming, and the Component Model Book migration guide is
published rather than forthcoming.

Syncs the active proposals tables with upstream Proposals.md: removes
I/O, which is no longer an active proposal, and renames GFX to WebGPU.
Adds the OCI registry requirement for Phase 2 entry and replaces the
Phase 4 and 5 descriptions, which the Subgroup has left undetermined.

Adds a WASI 0.3 patch releases table covering 0.3.0 and 0.3.1.

Adds a Contributing to WASI section to the contribute page, adds the
upstream process documents to resources, and removes the unused
HomepageFeatures boilerplate component.
Corrects the Wasmtime runtime support paragraph. The previous text dated
the wasmtime serve dual-world fallback to v44, when it has been present
since v41, and implied that v44 and v45 run released WASI 0.3.0 when they
vendor the 0.3.0-rc-2026-03-15 snapshot. Wasmtime 46 is the floor for
released 0.3.0.

Adds external-id to the WASI 0.3.1 changelog entry. The gate adopted at
the August 6 meeting covers implements and external-id together, so the
entry understated what a 0.3.1 runtime must implement.

Hoists the 0.3.1 implementation requirement out of the changelog cell
into the runtime support section, where implementers land, and links both
to the Component Model features section.

Corrects the claim that Subgroup meetings are open to anyone. They are
open to W3C WebAssembly Community Group members, which anyone can join.

Retitles the phases 4 and 5 bullet to match upstream, which leaves the
process to be determined, and collapses the two empty proposal tables
that restated the retired per-phase descriptions. Restores the other
Phase 2 entry criteria, corrects the Phase 3 heading to CG + WG, and
refreshes the WebGPU description, which described the old wasi-gfx
umbrella rather than the current package.
The releases table listed WASI 0.2 and 0.3 both as Stable with nothing to
choose between them, while language support for 0.3 is still landing.
Distinguishes the two, points readers at the Languages page, and notes
that a WASI 0.3 runtime also runs WASI 0.2 components.

Refreshes the 0.3 rows on the Languages page. Rust has WASI 0.3 bindings
in the wasip3 crate, which tracks released 0.3.0 and works from either
component target, so the previous "0.3 nightly" understated it. Describes
the jco preview3-shim as experimental, which is how the package describes
itself.
@ericgregory
ericgregory merged commit a900dc4 into bytecodealliance:main Aug 26, 2026
1 check passed
ericgregory added a commit that referenced this pull request Aug 26, 2026
Wasmtime snapshots: 41 and 42 vendor 0.3.0-rc-2026-01-06, not
0.3.0-rc-2026-03-15, which was published after both shipped. Splits the
range and names the final 0.3.0 specification explicitly.

Runtime compatibility: "a WASI 0.3 runtime also runs WASI 0.2 components"
stated as a guarantee what the roadmap describes as optional, met either
by implementing both versions or by polyfilling. Scoped to the runtimes
that do it, and the duplicate copy on the Languages page is removed.

Rust bindings: the wasip3 crate is written for wasm32-wasip3. It can be
used from wasm32-wasip2, but upstream recommends matching the crate to
the target, and libstd there is still WASI 0.2. The version column is
requalified to match how jco's 0.3 support is qualified in the same table.

Release cadence: drops the day of the week for the WASI 0.2 series. Seven
of those twelve releases shipped on a Thursday, and the timeline plots
those real dates. Replaces the prose shipped-or-planned note with a
Status column that cannot go stale unnoticed.

Phase process: the versioning section still gated 1.0 on reaching Phase 5
while the phase list says phases 4 and 5 are undetermined. Drops the (WG)
suffix asserting ownership of an undefined process, and notes where the
removed wasi:io proposal is documented.

Timeline: distinguishes planned releases from shipped ones, which were
drawn identically, and adds a dark theme palette. The previous gray was
3.56:1 on the dark background, below the 4.5:1 AA threshold.

Also corrects the WASI 0.2 launch vote date to January 25, 2024.
ericgregory added a commit that referenced this pull request Aug 26, 2026
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