chore(release): 1.5.3 - #171
Merged
Merged
Conversation
Six user-facing fixes since 1.5.2, all of them WordPress 7.1 fallout or found while testing against it. 7.1 keeps the toolbar on screen in the post and site editors, where it used to be hidden. That made Maestro's Edit Menu button reachable on screens with no admin menu to edit — and testing the fix surfaced three siblings of the same defect that predate 7.1: narrow viewports, the site editor dead end, and the inert Collapse menu button. Also fixes unsaved posts raising a browser "Leave site?" prompt when entering or leaving edit mode, by autosaving first. Autosave, never savePost: a published post keeps the version readers see. Version strings bumped by bin/prep-release.sh. readme.txt carries the changelog and Upgrade Notice in the plain user-facing voice the previous entries use — what changed and what it means for the reader, not the mechanism. This is the release that puts "Tested up to: 7.1" in front of users: the claim merged in #159 but wordpress.org serves the tag, and v1.5.2 predates it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
This is the release that puts
Tested up to: 7.1in front of users. The claim merged in #159, but wordpress.org serves the tag, andv1.5.2predates it — so the listing still reads 7.0 today. WordPress 7.1 ships now.What's in it
Six user-facing fixes since 1.5.2, all 7.1 fallout or found while testing against it:
savePost, so a published post keeps the version readers see.Testing the first fix is what surfaced the next three: they are the same defect — an entry point offered where it cannot work — and three of them predate 7.1 entirely.
Verification
Version strings bumped by
bin/prep-release.sh. Unit 167, JS 83, phpcs clean, doc-links clean. The full e2e suite ran green against a real 7.1-RC4-63322 build throughout this work (64 passed / 28 skipped at last run).After merge
Tag
v1.5.3on main to trigger the deploy. Until that tag exists, wordpress.org keeps serving 1.5.2 and showing "Tested up to 7.0".🤖 Generated with Claude Code