WordPress 7.0 RC4 just hit the servers, and it marks the final “hard string freeze” before the stable release on May 20, 2026. If you have been following the 7.0 cycle, you know it has been a bit of a rollercoaster, especially after the decision to pull the full real-time collaboration features for stability. Reaching RC4 means the core team is confident that the remaining bugs are minor.
As someone who has spent over a decade fixing sites that “just updated,” let me be clear: WordPress 7.0 RC4 is not for your production site. This is the phase where we break things in staging so we do not have a 2 AM emergency next week. RC4 mostly polishes the DataViews API and the new WP AI Client so they do not cause race conditions or memory bottlenecks.
Why WordPress 7.0 RC4 matters for developers
This release candidate is more than another version number. It brings some big architectural shifts. We are moving away from static admin list tables toward a React-based DataViews system. For developers, that means custom post types are about to get more interactive, but it also means some legacy hooks may need a refactor. The Abilities API also changes how we handle AI integration inside the block editor.
I previously wrote about why WordPress 7.0 real-time collaboration was pulled, and RC4 proves that stability was the right call. The focus now is on making PHP-only block registration work without a hitch. That is the feature I am most excited about, since it lowers the barrier for simple block development without the React overhead.
Technical testing: the WP-CLI way
You can use the Beta Tester plugin, but WP-CLI is the more reliable way to handle updates in a headless or automated environment. It avoids the timeout issues that sometimes hit the browser-based updater during large core shifts. Use the following command to pull the RC4 build into your local environment:
# Update to WordPress 7.0 RC4 via WP-CLI
wp core update --version=7.0-RC4If you are building custom functionality that relies on the new version, wrap your logic in a version check. I have seen too many “white screen of death” errors because a developer assumed a feature existed before it was officially merged. Check the $wp_version global before hitting new APIs.
<?php
/**
* Example: Checking for WordPress 7.0 specific features
*/
function bbioon_check_v7_compatibility() {
global $wp_version;
if ( version_compare( $wp_version, '7.0-RC4', '>=' ) ) {
// Safe to use new DataViews or AI Client logic
}
}
add_action( 'admin_init', 'bbioon_check_v7_compatibility' );What to watch in the Trac tickets
If you dig into the Core Trac tickets since May 8, you will see a focus on Gutenberg regression fixes, especially on how the new Grid block handles mobile reflowing. If you have custom layouts, test your CSS breakpoints against RC4 now. Version 7.0 is much more aggressive than earlier releases with its native aspect ratio handling.
You can also jump into the WordPress Playground to test these features without setting up a local server. It is a quick way to check a bug report without the “it works on my machine” headache.
If this WordPress 7.0 RC4 work is eating up your dev hours, I can handle it. I have been wrestling with WordPress since the 4.x days.
The final countdown to stable
We are just days away from the final release. My advice: spend tomorrow morning running your most complex site through RC4 on a staging server. Check the wp-content/debug.log for any new deprecation notices. It is better to fix a transient error now than to refactor an entire plugin on launch day.
