Release v7.0.0-beta.0 #6962
Open
Release v7.0.0-beta.0 #6962
+15
−14
Conversation
This file contains 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
michaelsproul
force-pushed
the
cut-v7.0.0-beta.0
branch
from
01ab145 to
efd1ed5
Compare
michaelsproul
changed the base branch from
unstable
to
release-v7.0.0-beta.0
michaelsproul
force-pushed
the
cut-v7.0.0-beta.0
branch
from
efd1ed5 to
f919394
Compare
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.
Proposed Changes
New release for Electra on Holesky and Sepolia.
Includes PRs:
Additional Info
The plan for this release is a little different, due to it being a beta release:
v7.0.0-beta.0feature PRs tounstableASAP (everything except this PR).release-v7.0.0-beta.0branch after all feature PRs are merged.release-v7.0.0-beta.0branch.unstableso we can unblock Fulu and other dev work.v7.0.0-beta.0by merging this branch torelease-v7.0.0-beta.0and tagging that release. DO NOT updatestableat this point, as we don't want to mark this beta release as stable, or have people auto-updating to it on mainnet.release-v7.0.0-beta.0tounstableso thatunstable's version increments to v7 as well.v7.0.0*releases from therelease-v7.0.0-beta.0branch, orunstableif deemed stable enough. If we want to unblock spicy merges tounstablesooner, we should maintain the v7 release branch separately, right up to the point of the stablev7.0.0release for mainnet.