Repository navigation
Release v0.23.3 manifest - #80
Merged
Merged
Conversation
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
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.
Release v0.23.3 manifest, for the
release/v0.23.3maintenance line (release-management section 7, maintenance line). This line is what mainnet runs; master carries v0.26.x.src/release-manifest.jsonis generated withbin/write-release-manifest.js --version 0.23.3from the pushed signed origin tags. Five components move to v0.23.3 and every other component keeps its v0.23.0 pin:Content-Encoding: brrequest bodies with 415; stays on Node 22.23.2 for the xchain-vm consensus runtime pinThe package version moves to 0.23.3 with one changelog entry. The
trainActivationblock carries no new height: nothing in this train changes derived state, and the mainnet activation census reads 0 values changed.The GitHub Release for v0.23.3 is published with
--latest=false, soreleases/latestkeeps resolving to the newest v0.26.x release and no node's no-refupdate allmoves backward.