WordPress 7.2 RC1: What to Test Before December 8

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, only fixes. It's still a test build, not an update for live sites. If you build themes, plugins or custom blocks, this is the one to test seriously.

This post covers RC1 only. I wrote up the earlier changes on my own site: Beta 1, Beta 2, Beta 3 and a running 7.2 release guide.

What does RC1 mean for WordPress 7.2?

Per the Make Core schedule, three things happen at RC1 that matter to developers:

• The 7.2 field guide comes out. It collects the dev notes for the release 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

Release parties are scheduled for 15:00 UTC (10 a.m. Eastern). Dates come from the WordPress 7.2 page and times from the release party schedule, both on Make Core.

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.

What's new in WordPress 7.2 RC1?

What should developers test in WordPress 7.2 RC1?

Start with the field guide, then re-test the changes most likely to touch existing code:

• NO_BACKSLASH_ESCAPES is turned off on the database connection. wpdb::set_sql_mode() now strips it from the session's SQL modes. Most sites won't notice. If you depend on that mode, the incompatible_sql_modes filter still works, but it has to live in a db.php drop-in because WordPress connects before plugins load.
• Admin scripts and styles load as separate files. Concatenation through load-scripts.php and load-styles.php is retired. Check anything that references those endpoints: firewall rules, CDN config, performance plugins.
• Admin menu and admin bar icons move from Dashicons to SVG. Admin CSS that colors or hides icons through ::before or .dashicons-* selectors needs a second look.
• Abilities API changes, including the new required_capabilities key from Beta 2.
• Custom InspectorControls against the DataForm-powered block inspector.

How do I test the release candidate?

Use a staging or local site with a fresh backup, then pick one:

1. WordPress Beta Tester plugin. Install it, then choose the "Bleeding edge" channel and the "Beta/RC Only" stream.

2. WP-CLI. Run this on the test site:
   

   wp core update --version=7.2-RC1 

3. WordPress Playground. Open the 7.2 RC1 instance in your browser. No setup, nothing to break.

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

WordPress 7.2 RC1 FAQ

When is WordPress 7.2 released?

December 8, 2026, with the release party at 15:00 UTC. RC2 (November 24) and RC3 (December 1) come first.

What is a WordPress release candidate?

A build that's feature-complete and close to final. After RC1, only bug fixes go in, and text is frozen for translators.

Where is the WordPress 7.2 field guide?

It's scheduled to publish on Make Core alongside RC1. Until then, the 7.2 dev notes are the place to look.

Is WordPress 7.2 RC1 safe for a live site?

No. Test it on staging or a local site. Live sites should stay on the latest stable release until December 8.

Before December 8

Three weeks from RC1 to final. If you find something broken, report it now: a fix has three release candidates to land in, and after December 8 it waits for 7.2.1.

What are you testing first? Tell me in the comments, especially if a plugin or theme of yours breaks on RC1.

Sources

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

AI disclosure: I drafted this post and used AI to help edit it. I checked the dates and technical claims against the sources above.