RATATOSKRATATOSK
Sign in

wasmCloud

v2.10.1Orchestration & Management
Sep 24, 2026

CHECK 1OTHER 4

A focused correctness release for version compatibility and WASI interface handling across deployment and development workflows. It includes runtime and development fixes for compatible version matching, with no new operator prerequisites or security changes announced.

Check if affected (1)

  • breakingPinned hostInterfaces version matching

    Applies if you pin a hostInterfaces entry to a WASI builtin version.

    Version-compatible matching for hostInterfaces entries now treats a pinned WASI builtin version such as wasi:random/random@0.2.2 as a requirement. Because the host provides the WASI base and no plugin serves that pinned entry, deployment now fails instead of ignoring the unmatched pin.

    github.com/…/588ab2103c13ff568ea8747742e4ea88f50b1395

All 4 other recorded changesfixes 4

fixes (4)

  • - **wash-runtime:** an unnamed WASI base entry is served by the host for an item when everything the item uses of it is unlabelled and at a version the host links (0.2.x and 0.3.x). Labelled imports and unsupported versions still bind a plugin. versions_compatible now follows wasmtime's canonical version rule exactly aka prerelease and 0.0.x versions match only themselves.
  • - **runtime-operator:** canonVersion no longer merges a prerelease into its minor track, so EnsureHostInterface keeps 0.2.6-rc.1 and 0.2.6 apart.
  • - **wash dev:** entries derived from components merge only at compatible versions and settle on the newest. Incompatible versions, e.g. wasmcloud:messaging@0.2.0 and @0.3.0, keep their own entries. A declared dev.host_interfaces version is left as written.
  • - A component importing a newer compatible WASI patch than the host links (e.g. 0.3.3 against the host's 0.3.0) is admitted and links.
Add wasmCloud to your stack

A weekly email arrives when a release needs action. Like the breaking changes in this release.

Add to stack →
Official release note ↗All wasmCloud releases →