(chore) Revert bump to the v17.5.1 (draft) due to bug in the release found by manual testing #58027
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
This reverts commit 501f6c8.
fullofcaffeine
added
[Type] Task
|
I am unsure if the label added is appropriate, but I found it was the best one that would somewhat fit this PR, given the description. Feel free to fix it if needed. |
fullofcaffeine
changed the title
|
Size Change: 0 B Total Size: 1.7 MB ℹ️ View Unchanged
|
|
Flaky tests detected in a6e54fb. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7588423973
|
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.
Why?
The fix #58016 for #57988, and the PR checks all passed (including all E2Es).
I started a draft for the patch release, and I always smoke test the zip before publishing, just in case. While testing the zip, I discovered it caused a BSOD in the Site Editor (see screecast below) and confirmed it to be a core issue, as I could reproduce it in a vanilla
wp-envinstance. Therefore, I'm wiping out/reverting the draft for 17.5.1. We will rerelease the patch release once we figure out a fix for that issue.Screen.Recording.2024-01-19.at.13.25.51.mov
How?
trunk.release/17.5branch and force-pushingv17.5.1draft release in Github (no need to delete the tag as it is only created when publishing).Next steps