Repository navigation
MESH v0.16.0
MESH v0.16.0 release notes
Prepared 2026-10-24 (not yet published: v0.15.0 is the latest release).
v0.16 adds no runtime behavior. It publishes what a renderer, a host and a debugger need to check replay: that a recorded session gives the same trees, byte for byte, in every MESH runtime and by every route to them.
Highlights
replay/in@valancex/mesh-conformance. The session-log format (replay/README.md), seven recorded logs and 1,000 random sessions. The format is line-JSON: aheader(the program's and the manifest's hashes, the initial snapshot),changes,event(what a PORT reported, the render it was drawn against, and the intent or diagnostic code the runtime returned),tree(a SHA-256 of the compact JSON, and the whole tree at every 50th line and at the end) and an informationalresult. Render versions are never recorded: they are process-local.- Three routes, both runtimes. A conforming player replays a log by an
update_changeschain, anupdatechain over whole snapshots and arenderof each snapshot, and requires the same hashes from each.cargo test -p mesh-runtime --test replay(the native runtime, which also records:MESH_BLESS=1) andpackages/mesh-runtime/test/replay.test.mjs(the WebAssembly package) both do; the 1,000 random sessions give the same digests in both.
Compatibility
Nothing changes in the compiler, the runtime, the manifest, render-v1, render-patch-v1 or template-v1/v2. @valancex/mesh-conformance gains files (conformance/replay/…); a consumer that reads the other directories is unaffected.
Release order
MESH 0.16.0 (its nine packages); then VALANCE, whose @valancex/conformance runs the logs (vlx replay) and records its own.
Verification
cargo test --workspace, cargo clippy --all-targets -- -D warnings, cargo fmt --check, RUSTDOCFLAGS="-D warnings" cargo doc, the grammar's parser regenerated with no difference, number_to_text.py --check; the runtime package's tests (including the replay test and the browser test with MESH_CHROMIUM), the compiler's and the conformance package's. The wrong-hash check of each player fails a log whose tree hash was changed.