docs(releases): mirror the v0.19.0 train - #41
Closed
jdogresorg wants to merge 1 commit into
Closed
jdogresorg wants to merge 1 commit into
jdogresorg wants to merge 1 commit into
Conversation
The releases page gains the v0.19.0 section: the first major train, the component table, the train boundary at testnet BTC 152787 and the per-chain XBRIDGE heights, in the shape the v0.18.0 section set.
Contributor
Author
|
Re-opened from a branch not named release/: the workflow resolves the indexer sibling at a release/ head ref, which this docs-only branch has no counterpart for. |
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.
Kit step 6d: operations/releases.md gains its v0.19.0 section (the first major train, the component table, the train boundary at testnet BTC 152787 and the per-chain XBRIDGE heights), in the v0.18.0 section's shape. check-release-mirror.js judges the page as published on master, so landing this on master is the step.