WordPress 7.0 RC2 has landed, which puts us in the quiet stretch before the April 9, 2026 ship date. Anyone following the Phase 3 roadmap knows this one is bigger than a point update: real-time collaboration and native AI orchestration both arrive in it. I have sat through enough messy releases, and the 5.0 Gutenberg launch is still the one everybody brings up. Skip the release candidate and you find out what broke on launch day, in production.
What is different about RC2
RC2 means the feature pile is closed and the work is refinement. The code is nominally ready, so the open question is whether the real-time collaboration features hold up under race conditions: what happens to database transients and heartbeat API performance when several people edit the same block at once. WordPress 7.0 RC2 is also the hard string freeze, so if you run multilingual sites, verify your translation files now.
The WordPress 7.0 RC1 post covered the highlights, but RC2 is where the AI Client and Connectors API fixes actually settle. Going through the Trac tickets closed since RC1, most of the movement is in block design tools and pattern editing interactivity.
Testing with WP-CLI
The Beta Tester plugin is fine for one site. With a fleet of staging sites you want WP-CLI, which is quicker and does not leave rows in your database to clean up later. Pull the RC2 build and see how your custom hooks and filters behave.
# The standard command to pull the latest RC2 build
wp core update --version=7.0-rc2
# Always verify the checksums after a dev-build update
wp core verify-checksumsFor a browser-only look, WordPress Playground needs no setup at all. It is good enough for a sanity check on the new real-time collaboration UI without editing a single server config file.
What to stress test
Three areas in WordPress 7.0 RC2 deserve your attention before the final release:
- Real-time collaboration: put two or more users on a complex block structure and watch for lag in the block locking mechanism.
- Pattern editing: content-only interactivity mode changed, so confirm your custom patterns still respect the
template_lockattribute. - Connectors AI: check that your AI-integrated plugins call the unified API properly. The WordPress 7.0 Roadmap post tracked these endpoints while they were still moving, and RC2 stabilizes them.
If the RC2 testing round is eating your dev hours, I can take it on. I have been wrestling with WordPress since the 4.x days.
Before April 9
Nobody wants to spend April 9 working through a flooded inbox. Grab the RC2 ZIP or run the command above, test the plugins you cannot afford to lose, and read the closed Trac tickets for anything that touches your stack. Then update the “Tested up to” line in your readme.txt. A boring, uneventful launch is the whole point, and it comes out of the testing you do now.
