- Fixed browser toolchain execution under strict Content Security Policy and kept isolated
Wasmer runtime preparation alive until it completes. - Aligned client execution with native language semantics, including Java compilation through
TeaVM WasmGC, QuickJS standard-library support, and Python 3.14.7. - Preserved deterministic execution by removing host-clock mode and corrected native Linux
parity checks to use file-backed standard input. - Fixed npm tarball publication paths and added release retries from existing immutable tags.
- Kept the execution contract at version 2. The seven code packages move together to 0.2.2;
independently versioned toolchain packages remain at 0.2.0.
Install the SDK with npm install @wasm-oj/sdk@0.2.2 or the CLI with npm install -g @wasm-oj/cli@0.2.2.
Full changelog: v0.2.1...v0.2.2
Companion toolchain release — 2026-09-10
All six independently versioned toolchain packages are published at 0.2.0, with an exact dependency on @wasm-oj/contracts@0.2.2:
@wasm-oj/toolchain-clang: updated cc1 settings and C++ precompiled headers.@wasm-oj/toolchain-python: CPython 3.14.7 and its updated runtime assets.@wasm-oj/toolchain-javascript: updated QuickJS and TypeScript Wasm assets.@wasm-oj/toolchain-java: WasmGC compiler and updated class libraries.@wasm-oj/toolchain-rustand@wasm-oj/toolchain-go: unchanged compiler assets, updated contracts dependency.
All toolchain verification and package publication workflows passed using the v0.2.2 source tag.