WordPress 7.2 RC1: Field Guide and What to Test

WordPress 7.2 RC1, the first release candidate, is scheduled for November 17, 2026. RC1 means the code is close to final: no new features from here, just fixes. It’s still a test build, not an update for live sites. If you build themes, plugins or custom blocks, this is the release to test seriously.

TODO after RC1 ships: confirm the actual release date and time from the WordPress News announcement and update this intro.

This post covers what changed in WordPress 7.2 RC1. For earlier changes, read my posts on Beta 1, Beta 2 and Beta 3, or the full WordPress 7.2 release guide.

What does RC1 mean for WordPress 7.2?

Per the Make Core schedule, three things happen at RC1:

• The 7.2 field guide comes out. It’s the full list of developer changes, dev notes and deprecations in one place.
• Hard string freeze. No more text changes, so translators can finish their work.
• The 7.2 branch is created. Trunk moves on to 7.3, and 7.2 only gets fixes from here.

WordPress 7.2 release schedule

TODO after RC1 ships: mark RC1 as out, and update any dates that changed.

Should you update live sites to WordPress 7.2 RC1?

No. Release candidates are for testing. Keep live sites on the latest stable release until 7.2 ships on December 8.

TODO after RC1 ships: check the latest stable version (7.1.4 as of November 8) and link to it.

What’s new in WordPress 7.2 RC1?

TODO after RC1 ships: summarize the RC1 announcement: fixes since Beta 5, any last features, and the Ipsum default theme status.

What should developers test in WordPress 7.2 RC1?

Start with the field guide. Then re-test the changes most likely to affect existing code:

• NO_BACKSLASH_ESCAPES turned off in the session SQL modes (from Beta 1).
• Admin scripts and styles loading as separate files instead of concatenated bundles.
• Abilities API changes, including the new required_capabilities key (from Beta 2).
• Custom InspectorControls against the DataForm-powered block inspector.
• Admin CSS that targets Dashicons as the admin moves to SVG icons.

TODO after RC1 ships: add the field guide link, the minimum PHP version (if it changed), every deprecation, and any dev notes published since Beta 5.

How do I test the release candidate?

Pick one of these, on a staging or local site with a fresh backup:

1. WordPress Beta Tester plugin. Install it, then choose the Bleeding edge channel and the Beta/RC Only stream.
2. WP-CLI. Run the command below on the test site.
3. WordPress Playground. Open the 7.2 RC1 instance in your browser. No setup, nothing to break.

wp core update --version=7.2-RC1

TODO after RC1 ships: confirm the exact WP-CLI version string from the announcement.

Found a bug? Report core issues on WordPress Trac and editor issues in the Gutenberg GitHub repository.

WordPress 7.2 RC1 FAQ

Before December 8

Three weeks to go. My WordPress release tracker follows 7.2 through release day, and it has the free 30-check checklist I run on client sites before every major update.

Sources

TODO after RC1 ships: add the RC1 announcement and the field guide.

• WordPress 7.2 (Make Core)
• WordPress 7.2 Release Party Schedule (Make Core)