Skip to content

Release v0.15.0 - xchain-vm - #8

Merged
jdogresorg merged 5 commits into
masterfrom
release/v0.15.0
Sep 7, 2026
Merged

Release v0.15.0 - xchain-vm#8
jdogresorg merged 5 commits into
masterfrom
release/v0.15.0

Conversation

@jdogresorg

Copy link
Copy Markdown
Contributor

Cuts xchain-vm for the v0.15.0 release train. 5 commits from master.

Changed

  • The sandbox, linter and authoring toolkit share one stripped-globals source of truth.

…uld reject

Four toolkit-simulator parity defects: GUARD_GAS_CEILING was hand-copied from
the indexer coin configs with no cross-repo pin, the authoring prompt taught a
stale partial copy of metering.RESERVED_IDENTIFIERS, ContractSimulator.deploy()
reproduced no part of the deploy gate so a deploy-rejected contract simulated
green on non-genesis networks, and the in-process default diverged from the
subprocess host-termination contract the chain runs under.

Review round 7 findings #6877, #6878, #6879, #6880. Also carries review round
6's vm work.
Review-round fixes, with each claim re-verified against current code.

Suite: 1064 passing, 0 failing (run on Linux; the isolated VM binding does not
load on macOS from the shared install).
The pinned 5.0.4 is affected by a critical ExternalCopy advisory. Moving to 6.2.0
across the vm and both of its consumers, which have to agree because the
consensus runtime pins an ABI and a validator fails closed against it.

The bump also removes a constraint rather than adding one. 5.0.4 had no prebuilt
binding, so every install compiled through node-gyp and the build failed on
newer Node for a removed V8 API, which is what bounded these repos to Node 22
and what makes a shared checkout hostile to two platforms at once. 6.2.0 ships
prebuilt bindings for both ABIs, so the dependency no longer sets the bound and
an install lands the right binding for the host that runs it.

Node 22 stays the bound for a different and still-live reason: the consensus
runtime pins process.versions.modules and the validator refuses any other ABI.
The engines rationale now says that rather than citing the build failure it no
longer has.

Adds a containment test over the isolate's reference surface, since a major
version of the isolation boundary is the wrong thing to take on trust.
@jdogresorg jdogresorg changed the title Release v0.15.0 Release v0.15.0 - xchain-vm Sep 7, 2026
@jdogresorg
jdogresorg merged commit 5dde39f into master Sep 7, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant