Repository navigation
docs: point the mainnet upgrade at events 1.8.0 - #168
Merged
Merged
Conversation
Mainnet now takes the 2.0.0 code as events 1.8.0 (tag events-v1.8.0) with profile 1.2.1, instead of 2.0.0. Runbook section 8 builds from that tag and lists the expected hashes, section 9 puts 2.1.0 after 1.8.0, and the backlog, threat model, custody policy, multisig guide, storage doc and README say the same. The version fields on this branch stay at 2.1.0 for testnet.
Plan expiredYour subscription has expired. Please renew your subscription to continue using CI/CD integration and other features. |
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.
Mainnet is not taking events 2.0.0 yet. It takes the same code as events 1.8.0, together with profile 1.2.1. This PR updates the docs on the default branch to say so. No code or version fields change here; this branch keeps building 2.1.0 for testnet.
The release source is tag
events-v1.8.0(commit7a7295fonrelease/events-1.8.0): commit 8b4f054 with only the events version label changed. It should not be merged anywhere, because doing so would relabel testnet's 2.1.0 code as 1.8.0.What changes in the docs:
Expected reproducible Linux hashes for the tag (
./scripts/build-release-linux.sh):acf70ca019f75ee6bc60f7806254dfb3508fd5a76634c708977e6030870dc6548a8a1208801c36f5d6e0b90eca4783f3d6789a10b26cf40b062782bfae5731c0Checked on the tag: fmt, clippy, 326 events and 60 profile tests, the mainnet guard tests, and the storage replay of real mainnet state through profile 1.2.1 and then events 1.8.0.