Skip to content

xchain-node v0.23.4

Choose a tag to compare

@jdogresorg jdogresorg released this 23 Oct 20:56
· 243 commits to master since this release
v0.23.4
d3fa4b5

Release v0.23.4 manifest, for the release/v0.23.4 maintenance line (release-management section 7, maintenance line). This line is what mainnet runs; master carries v0.26.x.

v0.23.4 is a dependency-only maintenance release: it clears the high-severity npm audit advisories on the v0.23.3 line. It changes no source, gate or consensus behaviour.

src/release-manifest.json is generated with bin/write-release-manifest.js --version 0.23.4 --reachable-from release/v0.23.4 from the pushed signed origin tags. Five components move to v0.23.4 and every other component keeps its v0.23.3 manifest pin:

Component Tag Change
xchain-decoder v0.23.4 npm dependency updates for audit advisories
xchain-encoder v0.23.4 npm dependency updates for audit advisories
xchain-utxo-tracker v0.23.4 npm dependency updates for audit advisories
xchain-hub v0.23.4 npm dependency updates for audit advisories
xchain-indexer v0.23.4 mariadb 3.5.4, proxy-addr 2.0.8, ip-address 10.7.4; stays on Node 22.23.2 for the xchain-vm consensus runtime pin
xchain-node v0.23.4 npm dependency updates and this manifest
xchain-vm, xchain-sync, xchain-explorer, xchain-sdk v0.23.0 unchanged
xchain-e2e-test, xchain-regtest-miner v0.21.0 unchanged
xchain-contracts v0.17.0 unchanged

Each changed package moves to 0.23.4 with one changelog entry. The indexer's compiled consensus version pin advances to 0.23.4 with its package, as it must; no protocol change is registered on that ordinal, so the enabled rule set does not move. The trainActivation block carries no new height, and the mainnet activation census reads 0 values changed and 0 newly armed.

The GitHub Release for v0.23.4 is published with --latest=false, so releases/latest keeps resolving to the newest v0.26.x release and no node's no-ref update all moves backward.