RATATOSKRATATOSK
Sign in

wasmCloud

v2.6.0Orchestration & Management
Jul 28, 2026

wasmCloud v2.6.0 is a feature-heavy release adding wash-runtime trigger services, host component plugins, warm-instance pooling, and P3 component support. Two behavior changes affect NATS messaging defaults and service replica load balancing. Wasmtime and wasm-tools are upgraded, along with numerous bug fixes.

  • breakingNATS messaging now uses consumer groups by default

    NATS messaging in wasmCloud now uses consumer groups by default in v2.6.0. If you have explicit consumer group configuration already in place, no action is needed. If you do not currently configure consumer groups and rely on the previous behavior, review your NATS setup to ensure the new default aligns with your messaging topology.

  • breakingService replica load balancing switched to round-robin

    Service replica load balancing across a host now uses round-robin ordering instead of random selection, fixing inconsistent replica assignment in v2.6.0. If your workloads depend on the random ordering of replicas per host, they will now receive requests in a predictable round-robin sequence.

Key changes (8)

  • NATS messaging now uses consumer groups by default (breaking behavior change)
  • Service replica load balancing switched from random to round-robin (breaking behavior change)
  • Adds trigger service support in wash-runtime with messaging ingress and routing
  • Adds host component plugin support including P3 component loader
  • Adds warm-instance pooling for components via pool_size and max_invocations settings
  • Adds P3 component build support via wash build
  • Upgrades wasmtime to v47 and wasm-tools to v0.253.0; disables Nagle's algorithm on HTTP connections for latency reduction
  • Plus: async secrets support via host component plugin, cross-store streams/futures, workload IP name lookup, and ~6 smaller bug fixes (blobstore timestamps, NATS batch cursors, duplicate workload rejection, span links/trace state, wit_world handler registration)
Add wasmCloud to your stack

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

Add to stack →
Source ↗All wasmCloud releases →