(chore) Revert the 16.7 RC2 release in order to release it again due to wrong changelog #54744
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
fullofcaffeine
changed the title
|
This also serves as documentation on how to revert a release in GB, if needed (as long as it wasn't pushed to the WP svn repo, yet!). |
|
Size Change: 0 B Total Size: 1.62 MB ℹ️ View Unchanged
|
|
Flaky tests detected in cdc4bcb. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/6278133311
|
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.
What?
Revert the changelog and version bump commits in trunk.
Why?
I released 16.7 RC2 today, but the changelog generated was wrong due to two commits listed there not being included in the release branch:
#52674 and #54720., but they were still listed in the changelog.
Since it's an RC, I think the cleanest way to go is to revert and release it again, or the asset s attached in the release will still contain the wrong changelog.
How?
trunkbranch (this PR)Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast