Repository navigation
NEXUS v0.13.0
NEXUS v0.13 release notes
v0.13.0
Prepared 2026-10-18 (nothing tagged or published: v0.12.3 is the latest release).
v0.13.0 is a minor release. It changes no API and no behavior of the runtime. It changes which MESH it is installed with.
Changes
- The
@valancex/mesh-runtimepeer range is^0.14.0. It was^0.10.0 || ^0.11.0 || ^0.12.0. A 0.x caret admits one minor only, so an application on MESH 0.14 (enums, presence tests and defaults, snippets) was told it had an unmet peer. The range is now the one range@valancex/common,@valancex/valanceand this package share (the Valance direction work's decision W20), so a plain install has one WebAssembly runtime, not two. The development dependencies are MESH 0.14 (@valancex/mesh-compilerand@valancex/mesh-runtime^0.14.0).
Compatibility
- API: unchanged. Behavior: unchanged.
- Install: narrower. An application on MESH 0.10, 0.11, 0.12 or 0.13 now has an unmet peer with this version; raise MESH to 0.14 with it (
pnpm add @valancex/mesh-runtime@^0.14.0), or stay on NEXUS 0.12.3. That is why this is a minor release and not a patch. - VALANCE, PORT: the VALANCE packages move to NEXUS
^0.13.0when it is released; PORT Web 0.10 accepts MESH 0.6 to 0.14.
Release order
MESH 0.14.0 (released), NEXUS 0.13.0, PORT Web 0.10.0, then the VALANCE packages.
Verification
pnpm typecheck, pnpm test (513 tests, 32 files) and pnpm build against MESH 0.14.0 from the registry. The range is pinned by tests/mesh-runtime-compat.test.ts (every alternative is ^0.minor.patch; the installed runtime's minor is admitted; one runtime in the lockfile). npm publish --dry-run of the packed tarball passes. Not verified: the VALANCE packages against NEXUS 0.13 (they are not released against it yet).