Release v0.3.1 · WebAssembly/WASI · GitHub
//releases/show" data-turbo-transient="true" />
Skip to content
Type / to search
Sign in<br>Sign upAppearance settings
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
Uh oh!
There was an error while loading. Please reload this page.
WebAssembly
WASI
Public
Notifications<br>You must be signed in to change notification settings
Fork<br>326
Star<br>5.8k
v0.3.1
Latest
Latest
Compare
Choose a tag to compare
Sorry, something went wrong.
Filter
Loading
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
No results found
View all tags
ricochet
released this
11 Aug 18:28
v0.3.1
59e48bf
This commit was created on GitHub.com and signed with GitHub’s verified signature .
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.
Today we’re releasing WASI 0.3.1. This is the first point release in the 0.3.x series, which we’ll be releasing every two months. See the release schedule for all planned releases through 2027.
The highlights for this release are the addition of implements and map dependencies in the component model. That means additional expressivity to WIT interfaces. For example: with implements it allows a component to import (or export) more than one instance of the same interface under distinct names. We might want to say we aren’t just importing any key-value interface, but more specifically a valkey interface for remote storage and an in-memory cache.
map brings a first-class associative dictionary type to WIT. This makes it possible to express dynamic sets of keys and values directly from WIT, replacing the previous pattern of needing to write list>.
Starting with 0.3.1, WIT interfaces in WASI are allowed to make use of these features. And both runtimes and toolchains must support these features in order to be compatible with WASI 0.3.1 or later. See our process documentation for more on this.
What's Changed
Require OCI package available for phase 2 entry by @yoshuawuyts in #938
Update wasi-gfx to wasi-webgpu by @yoshuawuyts in #939
Allow re-casing when serializing for transmission by @cceckman-at-fastly in #926
Document release train by @yoshuawuyts in #945
Add process for adopting Component Model features by @ricochet in #941
Adopt Component Model map and implements features for 0.3.1 by @ricochet in #950
New Contributors
@cceckman-at-fastly made their first contribution in #926
Full Changelog : v0.3.0...v0.3.1
Contributors
ricochet, yoshuawuyts, and cceckman-at-fastly
Assets
Loading
Uh oh!
There was an error while loading. Please reload this page.
-->
👍<br>alexted reacted with thumbs up emoji<br>😄<br>alexted reacted with laugh emoji<br>🎉<br>alexted and nico-arianto reacted with hooray emoji<br>❤️<br>alexted reacted with heart emoji<br>🚀<br>Viir and alexted reacted with rocket emoji<br>👀<br>alexted reacted with eyes emoji
All reactions
👍<br>1 reaction
😄<br>1 reaction
🎉<br>2 reactions
❤️<br>1 reaction
🚀<br>2 reactions
👀<br>1 reaction
3 people reacted
You can’t perform that action at this time.