By Grim
WAIT — Affects you if you build or look after WordPress sites
WordPress 7.2 Release Candidate 1 is out now. It arrived on November 17, and it is the first version of 7.2 that WordPress thinks is nearly done.
A Release Candidate — RC for short — is WordPress saying, “We think this is nearly finished, please go try to break it.” It is still under development. WordPress is clear about it: do not install, run, or test it on production or mission-critical websites. Production just means a real, live site that real visitors depend on. For this one, use a test server and a test site instead.
The final release is scheduled for December 8, 2026. Release Candidate 2 followed a day later, on November 18. RC3 is scheduled for November 24 and RC4 for December 1, ahead of the final release on December 8. Between now and then, the job is bug fixes, accessibility improvements, and compatibility updates — not big new features.
RC1 itself brings fixes since Beta 5 for things like client-side media uploads, the new random-content redirect feature, plugin dependency messages, and better keyboard navigation through a skip link in the admin bar. A skip link is the little helper that lets keyboard users jump past the menus and straight to the content, instead of tabbing through everything first.
Why it matters for site builders
RC1 is your early warning to test, not your cue to update. If you build sites for other people, this is the window where you find out — on a copy, not on their live site — whether your usual setup plays nicely with 7.2.
That matters more than usual this time because 7.2 touches a lot of the stuff you use every day: the block editor, media uploads, Global Styles, and the admin itself. Finding a weird gallery behavior or a broken upload flow on a test site in November is a small fix. Finding it on a live site on December 8 is a panicked phone call.
And before you test anything, back up. The same routine as installing anything new — our plain-words safety check walks through it: “Before You Install That Plugin: A Plain-Words Safety Check“
My take
I like this stage of a release. Nothing is urgent, and you get to be curious instead of rushed. Spin up a copy, click around the bits your clients actually use, and make a little note of anything odd. That’s it.
Don’t chase every new feature on day one, either. They’ll still be there after the final release. The builders who have the calmest December are the ones who tested quietly in November.
Bottom line:
Affected: Anyone who builds, maintains, or hosts WordPress sites. Not a must-install yet.
Urgency: Low. Wait for the final release.
What to do: Test 7.2 RC1 on a test site only — never on a live or mission-critical site. Grab it with the WordPress Beta Tester plugin (Bleeding edge channel, Beta/RC Only stream), or download the RC1 zip from wordpress.org, or run wp core update –version=7.2-RC1. Save real updates for the final release scheduled for December 8.
Tested at the Forge: every claim in this piece was checked against the sources below.
Sources:
https://wordpress.org/news/2026/11/wordpress-7-2-release-candidate-1/