XChain Platform v0.12.2

XChain Platform v0.12.2.

A patch train that moves the carrier alone. src/release-manifest.json pins xchain-node at v0.12.2 and the other twelve components at the tags they already carry, unchanged. A component's version is the platform version at which it last changed, so a gap means unchanged that release, not skipped.

Verifying this release

gpg --verify SHA256SUMS.asc SHA256SUMS
shasum -a 256 -c SHA256SUMS

The signing key is published at xchain-documentation/operations/release-signing.md and in tools/release/ in every train repo. Any other key is not an official release.

Installing this exact set

xchain-node install v0.12.2 <service> <coin> <network>

What is in this train

• validator init, stake and unstake: generate the identity and both funding wallets, then mint, stake and withdraw against the public network. An operator can join before installing any stack. v0.12.1 shipped without these while the documentation described them, so someone following the quickstart was told the command did not exist.
• An unrecognised service name is refused with the list of valid ones. It previously expanded to every service on every coin and network, silently.
• A coin image builds from a context that actually holds its Dockerfile, and no longer writes live credentials into the tracked config template.
• A mutating command waits out a busy lock instead of losing the run, and a locked bootstrap create is retried by the publisher rather than reported as a failure of the publishing machinery.
• The next step printed after validator init names the release rather than a branch.

Everything here is state-neutral: operator tooling, argument handling, build context and lock behaviour. Nothing changes what state is derived from existing bytes.

Full per-component detail is in each repository's CHANGELOG at its tag.