docs(releases): mirror the v0.20.0 train - #46
Merged
Merged
Conversation
Adds the v0.20.0 section to the release mirror, newest first, linking its own tag on the node Release page. Component versions come from the tagged release manifest and the activation heights from the canon protocol constants at the v0.20.0 tag.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the missing
v0.20.0section tooperations/releases.md, so the published mirror at docs.xchain.io/operations/releases no longer ends at v0.19.1 while v0.20.0 is live.The section follows the shape of the existing v0.19.x entries: a dated line linking the train's own tag on the node Release page, a prose summary, the thirteen-row component table, and the activation and roll-order notes.
Every value in it was read from a shipped artifact rather than from prose:
src/release-manifest.jsonat thev0.20.0tag. The manifest pins eleven moved repos plusxchain-contractsat v0.17.0 (unchanged, and it carries no v0.20.0 tag);xchain-nodeis the carrier and is not listed in its own manifest, so its 0.20.0 comes from itspackage.jsonat the tag.trainActivation.heights.testnet, classificationmajor, rule set 0.20.0.protocol/constants.jsat thev0.20.0tag: producer BTC 153222 / LTC 4891504 / DOGE 67911796, consumer BTC 153266 / LTC 4891766 / DOGE 67912575, anchor-attestation barrier BTC 153266. Every mainnet entry is null, so mainnet is unarmed on every row.releasedfield.Thirteen repositories carry a signed
v0.20.0tag;xchain-contractsis unchanged and does not.The mirror gate reads the published copy on
master, so this has to merge before it goes green.