Skip to content

Release v0.9.0 - #20

Merged
jdogresorg merged 2 commits into
masterfrom
release/v0.9.0
Aug 14, 2026
Merged

Release v0.9.0#20
jdogresorg merged 2 commits into
masterfrom
release/v0.9.0

Conversation

@jdogresorg

Copy link
Copy Markdown
Contributor

XChain Platform 0.9.0

First cut of the platform release train. Every train component adopts the shared
platform version stream in this release.

What changes here

  • package.json / package-lock.json version set to 0.9.0
  • CHANGELOG.md gains the 0.9.0 entry, above a marker line separating the
    legacy version stream

The version goes DOWN, on purpose

The platform stream starts at 0.9.0 for the testnet series; 1.0.0 is reserved
for mainnet. For most components that is a lower number than their legacy version
but a newer release. The changelog marker says so in place, because otherwise
it reads as a regression to anyone scanning it.

Gate

GitHub Actions cannot start jobs on this org, so the green evidence for this PR
is the venue gate that ran on this exact commit at push time. Tallies are in the
release notes.

First release of the XChain Platform release train. Every train component
now shares one platform version, so "XChain 0.9.0" names an exact,
reproducible set of software.

The number moves backward for most components, which is deliberate: the
platform stream starts at 0.9.0 for the testnet series and 1.0.0 is
reserved for mainnet. The changelog carries a marker line above the old
entries, because a higher legacy number is an older release and that will
otherwise read as a regression.
@CLAassistant

CLAassistant commented Aug 14, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

Written from the actual tagged merge commits of the eight sibling repos,
which is why this repo cuts last: the manifest records the commit each tag
points at, and those commits do not exist until the merges do.

The shipped-manifest test changes shape with it. Asserting the component
set is empty was correct right up to this cut and is now wrong; what has
to hold from here is that every pin is usable, so it checks a full 40-hex
commit and a tag matching the train, and that the carrier does not pin
itself.
@jdogresorg
jdogresorg merged commit 64027c0 into master Aug 14, 2026
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.

2 participants