Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release v7.0.0-beta.0 #6962

Merged
merged 1 commit into from
Feb 13, 2025
Merged

Release v7.0.0-beta.0 #6962

merged 1 commit into from
Feb 13, 2025

Conversation

michaelsproul
Copy link
Member

@michaelsproul michaelsproul commented Feb 10, 2025

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:

  • 1. Merge all v7.0.0-beta.0 feature PRs to unstable ASAP (everything except this PR).
  • 2. Branch off a release-v7.0.0-beta.0 branch after all feature PRs are merged.
  • 3. Re-target this PR at release-v7.0.0-beta.0 branch.
  • 4. Resume merges to unstable so we can unblock Fulu and other dev work.
  • 5. Release v7.0.0-beta.0 by merging this branch to release-v7.0.0-beta.0 and tagging that release. DO NOT update stable at this point, as we don't want to mark this beta release as stable, or have people auto-updating to it on mainnet.
  • 6. Back-merge release-v7.0.0-beta.0 to unstable so that unstable's version increments to v7 as well.
  • 7. Create subsequent v7.0.0* releases from the release-v7.0.0-beta.0 branch, or unstable if deemed stable enough. If we want to unblock spicy merges to unstable sooner, we should maintain the v7 release branch separately, right up to the point of the stable v7.0.0 release for mainnet.

@michaelsproul michaelsproul added do-not-merge v7.0.0-beta.0 New release c. Q1 2025 labels Feb 10, 2025
@michaelsproul michaelsproul requested a review from jxs as a code owner February 10, 2025 00:53
@michaelsproul michaelsproul changed the base branch from unstable to release-v7.0.0-beta.0 February 10, 2025 04:12
@michaelsproul michaelsproul force-pushed the cut-v7.0.0-beta.0 branch 2 times, most recently from f919394 to 2b1c992 Compare February 12, 2025 06:13
@michaelsproul michaelsproul added ready-for-merge This PR is ready to merge. and removed do-not-merge labels Feb 13, 2025
@michaelsproul
Copy link
Member Author

@mergify queue

Copy link

mergify bot commented Feb 13, 2025

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 1888be5

@mergify mergify bot merged commit 1888be5 into release-v7.0.0-beta.0 Feb 13, 2025
30 checks passed
@mergify mergify bot deleted the cut-v7.0.0-beta.0 branch February 13, 2025 03:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-merge This PR is ready to merge. v7.0.0-beta.0 New release c. Q1 2025
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants