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:
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.
The best evidence that we're on the right innovation path is the growing interest in wasmCloud from a variety of industries. wasmCloud has come a long way in the last 12 months alone and, as we approach the release of wasmCloud 1.0, the industrial use cases for our platform are quickly emerging.
Last week, we looked back at how far the wasmCloud project has come. In particular, the progress made in the last few months since the Q3/Q4 roadmap was published. We’re nearing the release of wasmCloud 1.0; our stable, standards-led and production-ready release due to be unveiled in early 2024. As we reach this major milestone, we’re excited to unveil a refreshed roadmap for Q1 2024.
As core contributors and maintainers of the popular CNCF project, wasmCloud, we’re excited to work towards the next major milestone in the evolution of this awesome community platform. In the next couple of posts, we’ll take a look back at how far we’ve come, and look ahead to what we can expect from wasmCloud 1.0; our standards-led, production-ready release due to be unveiled in early 2024.
wasmCloud now comes with experimental support for Go, via TinyGo compiler, taking full advantage of the WebAssembly component model. This is an exciting moment as, for the first time, Go developers can build cloud native Wasm applications with components and run them in wasmCloud in an open, dependency-free and standards-based way.
This year, wasmCloud is getting into the spooky spirit by participating in Hacktoberfest! Our primary development repositories all feature the hacktoberfest topic. Whether you’re interested in your first open source contribution, learning Rust for the first time, getting involved with a WebAssembly project or seasoned in all of the above, you’re invited to participate!
We're a big fan of bumping minor versions here at wasmCloud. When we released our first version of the Elixir/OTP host, we bumped from 0.18.0 to 0.50.0 just to make it extra clear that this was a big change. Today, we're making a similar bump to 0.78.0, and this blog post will explain why.
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.