The WordPress 7.0 Release schedule moved again. If you follow the Make blog you have already seen it: the general release date is now May 20th, 2026. “Necessary architectural improvements” usually translates to something closer to “the foundation cannot carry the Phase 3 collaboration features yet.” I have watched that happen on enterprise builds. You do not ship a broken media processing pipeline to hit a date.
RC3 is being treated as a beta
The next version is labeled RC3, but the release squad is treating it as a new Beta 1. That means the feature freeze is not as frozen as the label suggests. If you run hosting or maintain high-traffic legacy sites, plan around it. The admin interface is shifting and DataViews has been rebuilt in React, so transients and race conditions can surface in code you have not touched in years.
This release also drops PHP 7.2 and 7.3. The WordPress 7.0 Release sets the floor at PHP 7.4.0, so anything older is a hard break rather than a deprecation notice. Do a dry run on staging with WP-CLI and find the incompatibilities while they are still cheap to fix.
# How to safely test the WordPress 7.0 Release Candidates
wp core update --version=7.0-RC3 --forceTesting on the host side
The call for host testing carries more weight this cycle. With the move toward an agnostic AI infrastructure layer and the Abilities API, WordPress talks to server-side resources differently than it did. If you plan to run the real-time collaboration features, check your Nginx or Apache configs against the new timeout thresholds.
I have argued before that architectural integrity trumps deadlines, and this schedule change suggests the core team reads it the same way. A delay is easier to absorb than a broken site on launch day. For the branching details, there is also my write-up on RTC pivots in 7.0.
If the WordPress 7.0 release is eating your dev hours, I can take it on. I have been working with WordPress since the 4.x days.
What to do before May 20
The WordPress 7.0 Release changes enough under the hood to earn real testing time. Treat RC3 as a beta, audit your PHP versions now, and drop into the release parties in the #core Slack channel if you hit bugs in the media pipeline. The official WP-CLI core update docs cover managing test environments.
