Skip to content

NEXUS v0.12.3

Choose a tag to compare

View all tags
@github-actions github-actions released this 14 Oct 01:13
· 53 commits to main since this release
v0.12.3
b49b740
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

NEXUS v0.12.3 release notes

Prepared 2026-10-13 (nothing tagged or published: v0.12.2 is the latest release).

v0.12.3 is a patch release. It changes no API and no behavior of the runtime.

Changes

  • The @valancex/mesh-runtime peer range accepts MESH 0.11 and 0.12. It was ^0.10.0; it is now ^0.10.0 || ^0.11.0 || ^0.12.0. A 0.x caret admits one minor only, so an application on MESH 0.11 (blocks: {#if} and {#each} replace the mesh-if and mesh-each elements) or on MESH 0.12 (formatting in the language server) got a peer warning, and with VALANCE 0.9 or later, which requires the 0.11 line, two runtimes could be installed. With the new range there is exactly one, the one the application supplies and initializes.
  • The tests use blocks. The keyed-repeat test in tests/mesh-runtime-compat.test.ts writes its repeat as {#each ids as item (item.id)}, and the development dependencies are MESH 0.11 (@valancex/mesh-compiler and @valancex/mesh-runtime ^0.11.0).

Compatibility

  • API: unchanged. Behavior: unchanged.
  • Install: additive. An application on MESH 0.10 keeps working; MESH 0.11 and 0.12 are now accepted. Declare the runtime yourself (pnpm add @valancex/mesh-runtime@^0.12.0).
  • MESH 0.11 and later reject the mesh-if, mesh-each and mesh-switch elements (retired-element): templates passed to Mesh.host that use them must be rewritten as blocks, in the MESH upgrade, not in NEXUS.
  • VALANCE, PORT: VALANCE 0.10 and PORT Web 0.4.2 accept the same MESH lines.

Release order

MESH 0.12.0, then NEXUS 0.12.3, PORT Web 0.4.2, VALANCE 0.10.0 (see the VALANCE repository's docs/releases/release-set-2026-10-b.md).

Verification

pnpm typecheck, pnpm test (513 tests), against MESH 0.11 from the registry. The range itself 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).

Assets 3
Loading