feat(docs): update site for P3 - #58
Merged
Merged
Conversation
Signed-off-by: Eric Gregory <eric@cosmonic.com>
…resh Signed-off-by: Eric Gregory <eric@cosmonic.com>
The Languages page (merged via PR bytecodealliance#55) referenced the flat docs/interfaces.md page, which this branch replaces with the docs/releases/ tree. Repoint both references to releases/index.md so the build resolves after PR bytecodealliance#58 lands. Signed-off-by: Eric Gregory <eric@cosmonic.com>
Recent ungating PRs (wasi-testsuite #248-#254) have brought P3 coverage to a regularly green state on Wasmtime and jco across Linux, macOS, and Windows. Reflect that in the page. Signed-off-by: Eric Gregory <eric@cosmonic.com>
ricochet
reviewed
Jun 12, 2026
ricochet
reviewed
Jun 12, 2026
ricochet
reviewed
Jun 12, 2026
Co-authored-by: Bailey Hayes <ricochet@users.noreply.github.com>
Co-authored-by: Bailey Hayes <ricochet@users.noreply.github.com>
Bring the WASI P2 patch releases table up to date with the three patch releases that have shipped since 0.2.9. Signed-off-by: Eric Gregory <eric@cosmonic.com>
WASI 0.3.0 was released on 2026-06-11, and upstream PR #929 collapsed the wit-0.3.0-draft/ directories and 0.3.0-rc-2026-03-15 / 0.3.0-draft identifiers down to 0.3.0. Update the WASI.dev pages accordingly: - Drop release-candidate framing on the WASI P3, roadmap, and introduction pages. - Update the WIT version pin from 0.3.0-rc-2026-03-15 to 0.3.0 on the WASI P3 and languages pages. - Point the resources page at the canonical wit/ directories. Signed-off-by: Eric Gregory <eric@cosmonic.com>
Now that WASI 0.3.0 is shipped, the roadmap framing of the 0.3.x line reads forward from "After 0.3.0 is released" to "With 0.3.0 released." Bump the Wasmtime support floor from 43+ to 44+ (when `wasmtime serve` gained P3 support and `wasi:tls` landed) and note jco's preview3-shim package, with futures support actively landing. Signed-off-by: Eric Gregory <eric@cosmonic.com>
ericgregory
changed the title
Signed-off-by: Bailey Hayes <bailey@cosmonic.com>
Signed-off-by: Bailey Hayes <bailey@cosmonic.com>
ricochet
approved these changes
Jun 12, 2026
rajsite
reviewed
Sep 6, 2026
|
|
||
| * **WASI P1 modules** import the `wasi_snapshot_preview1` functions but operate only on the resources the runtime hands them at startup, chiefly preopened file descriptors. A module can call `fd_read` but only against the descriptors it has been given, and there is no way to ask for a new one. Capability granting happens at runtime invocation, not in the module binary. | ||
| * **WASI P2 components** express capabilities directly in WIT. Each capability (filesystem access, networking, environment, clocks, randomness) is a separate import, and the host instantiates the component with only the imports it has granted. The component's interface contract is the capability surface, and it is statically inspectable in the component binary itself. | ||
| * **WASI P3 components** continue to refine this model. Capabilities that P2 required guests to thread explicitly through each call (such as the `wasi:sockets/network` handle passed into `bind`, `connect`, and DNS lookups) are implicit at the world level in P3. The host still grants network access at the world boundary; guests no longer plumb the handle through every operation. |
Contributor
There was a problem hiding this comment.
Landed on this recently, don't think I follow what is being described for p3.
The host still grants network access at the world boundary; guests no longer plumb the handle through every operation.
Reading this makes it sound like we lost the ability to control capabilities that are passed to component dependencies (i.e. wasi-virt style control to filter, i.e. file access or block host provided capabilities) but I don't believe that's the case is it?
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
3 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.
Updates the site ahead of the P3 release: