5 posts tagged with "Wasm"

We’re excited to see our friends again as we embark on a whistle-stop tour of two of our favorite European events (and cities) in the 2024 conference calendar: WASM I/O, Barcelona and KubeCon + CloudNativeCon Europe 2024, Paris. With the release of WASI 0.2 and the WebAssembly component model, we’re taking wasmCloud 1.0 on tour—introducing it to cloud native developers, and platform engineers, as the best place to bring components to life in production environments.

We’re proud to announce wasmCloud 0.82—the last stop on the road to our 1.0 milestone. This release is all about preparing the way, bringing:

• Full and stable support for WASI 0.2 APIs
• Quality-of-life improvements for builds and deployment
• Support for OpenTelemetry logging
• Additional bug-fixes and improvements

WASI 0.2.0 is in the wild, pushing forward common standards for portable, language-agnostic components and interfaces. That means it just got a whole lot easier to create WebAssembly components from any language—and have them work together with other components of any provenance. Better still, it's now possible to "bring your own Wasm components" from any language that compiles to WASI 0.2.0 and run them as distributed apps in wasmCloud.

WASI Preview 2 officially launched! After a vote in the WASI Subgroup of the W3C WebAssembly Community Group, the standard set of interfaces included in the launch of Preview 2, aka WASI 0.2.0, is ready for use by library implementers. We've been closely tracking the different release candidates of WASI 0.2.0 over the last 6 months, and wasmCloud will update its runtime WIT definitions to the pinned versions in just a few days.

wasmCloud uses GitHub actions to publish all of its example WebAssembly modules and first-party capability providers to AzureCR. Neither of these are actual containers, nevertheless they conform to the OCI image specification and can be distributed well with the existing OCI tooling in the cloud native ecosystem.