docs: document the release train and Component Model feature adoption - #62
Merged
ericgregory merged 4 commits intoAug 26, 2026
Conversation
Brings two WASI Subgroup process documents onto the site. Roadmap: corrects the point release cadence to the second Tuesday of every second month, notes the first Tuesday cadence the WASI 0.2 series ran on, and adds the scheduled release dates through WASI 0.3.9. Releases: adds a Component Model features section covering the adoption process, the cumulative implementation requirement, and the adoption record through WASI 0.3.1, including the map and implements features adopted at the August 6, 2026 Subgroup meeting. Sources: docs/Release.md and docs/ComponentModelFeatures.md in the WASI repository.
Roadmap: corrects the Wasmtime floor for WASI 0.3 from 43 to 46. Wasmtime 43 through 45 vendor the 0.3.0-rc-2026-03-15 snapshot rather than released 0.3.0, so a component built against 0.3.0 does not run on them. Scopes the WASI 0.2 cadence claim to 0.2.1 through 0.2.12, since seven of the twelve 0.2.x releases shipped on a Thursday. Marks 0.3.0 as a one-off release in the schedule table and retitles the table, which lists shipped releases as well as planned ones. Standardizes on "patch release" to match Release.md and the WASI 0.2 page, and dates the projected 0.3.x feature list. Releases: drops the emoji gate column, which conveyed nothing to a screen reader and duplicated the feature names beside it. Restores the clause stating that adopted features may be used by APIs in that release and later, the second case in which proposals may experiment with unadopted features, and the upstream issue links.
ericgregory
marked this pull request as ready for review
August 26, 2026 14:03
Redraws the timeline as an SVG. The previous image showed WASI 0.3.0 as a projection at the right edge of 2026 and used the retired P2 and P3 labels. The replacement shows the shipped releases and the scheduled train, is legible in both themes, and is reviewable in the diff. Replaces the February 2025 feature projection, which WASI 0.3.1 did not deliver on, with what 0.3.1 actually adopted and how later features reach a release.
Replaces the span bracket, which had been shortened to avoid overlapping the 0.3.0 marker and so ended two months early. Ticks are accurate to the published dates and match how the 0.3.x train is drawn.
ricochet
approved these changes
Aug 26, 2026
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.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Brings the WASI Subgroup's release train and Component Model feature adoption process onto the site, with the schedule through 2027 and the adoption record through 0.3.1. Also redraws the project timeline, which showed 0.3.0 as a projection, and replaces the February 2025 feature forecast that 0.3.1 did not deliver on.
Merge before #63, which links to the Component Model features section added here.