WordPress 7.0 RC5 just hit the servers. If you have been following the 7.0 development cycle, you know the release is close. An “RC5” still tells you something specific. A fifth candidate means the core team is catching edge cases that would otherwise surface on someone’s production site.
This version is still under development, so do not run WordPress 7.0 RC5 on a live site. Run it anywhere real and you volunteer to be the person who finds a race condition the hard way. Spin up a staging environment instead, or use the browser-based Playground, and watch how the new Gutenberg refinements and AI integrations behave against your own stack.
Why a fifth release candidate is good news
The core team usually aims for two or three release candidates. A fifth one means the testing is doing its job. Bugs found since RC4 get fixed now instead of shipping as “known issues” on May 20th. If you already worked through testing WordPress 7.0 RC4, this build settles a few more Trac tickets and Gutenberg commits that turned up last week.
The reference point is still the WordPress 7.0 Field Guide. It covers the architectural changes behind this release, including the Interactivity API updates and DataViews. Then check the closed Trac tickets to see whether a bug that hits your own workflow has been fixed.
How to safely test WordPress 7.0 RC5
If you would rather stay in the terminal than click around the dashboard, WP-CLI handles this in one line. It is also the cleanest way to update a staging site without leaving plugin transients behind. Pull the latest candidate with:
wp core update --version=7.0–RC5If you want a dashboard route, use the WordPress Beta Tester plugin and set the channel to “Bleeding edge” and the stream to “Beta/RC Only”. If you are curious but do not want to touch a server, the WordPress Playground instance holds up well for testing block registration logic or theme compatibility.
On one project we skipped RC testing for a major 5.x release. The checkout broke, because a filter we relied on had its priority changed at the last minute. Don’t be that dev. Test your hooks and filters against WordPress 7.0 RC5 now, while you still have a few days to refactor.
If WordPress 7.0 RC5 testing is eating your dev hours, I can take it off your plate. I’ve been working with WordPress since the 4.x days.
Counting down to May 20th
We are days away from the full launch. AI-assisted patterns will get the headlines, but WordPress 7.0 RC5 is about the boring work of stability, backward compatibility and performance fixes. There is also more on how the Presence API is shaping up in this cycle.
Testing only works if people report what they find, so file anything you hit in the Alpha/Beta forums or on Trac. A reproducible bug fixed this week costs far less than a support queue full of them on launch day. Happy testing.
Five candidates in
the bugs run out of places
to hide before launch
