wasmCloud

v2.10.3Orchestration & Management

2026년 10월 2일

의존성 업데이트와 워크로드 및 플러그인 상태 정합성 수정에 초점을 둔 유지보수 릴리스입니다. 운영자 설정 변경은 발표되지 않았습니다.

그 외 기록된 변경 9건 전체fixes 8 · value changes 1

* fix(wash-runtime): release per-workload state that outlived unbind by @ricochet in https://github.com/wasmCloud/wasmCloud/pull/5634
* fix(runtime-operator): stop orphaning workloads around failed stops and departing hosts by @ricochet in https://github.com/wasmCloud/wasmCloud/pull/5632
- **postgres never released anything at unbind.** Unbind removed entries whose component id *started with* the workload id. Component ids are fresh UUIDv7s, so nothing ever matched. - The existing test used made-up ids like workload-a-component-0, which hid the bug; it now uses real UUIDs.
- **wasi:logging had no on_workload_unbind.**
- **A plugin failure during start could free the workload id too early.**
- **unbind_all_plugins stopped at the first HTTP unbind error.**
- **Egress state outlived workloads that serve no HTTP.** The HTTP handler heard about a stop only for components exporting wasi:http, and the service unbind never reached the egress transport. A messaging handler or service that *sent* HTTP kept its pooled connections, TLS session store and connection permits until idle expiry (60s). The handler is now notified once for every stopping workload.
- **In-memory keyvalue and blobstore recreated storage after unbind.**

* build(deps): Bump the all-go group across 2 directories with 10 updates by @dependabot[bot] in https://github.com/wasmCloud/wasmCloud/pull/5635

wasmCloud 스택에 추가

조치가 필요한 변경이 나오면 주간 메일로 받아볼 수 있습니다. 이번 릴리스처럼 조치가 없는 주에는 메일을 보내지 않습니다.