Following the launch of WordPress 7.0, contributors monitoring the WordPress.org support forums, Trac (the project’s bug-tracking system), and the Gutenberg GitHub repository found enough issues to warrant a dedicated maintenance release.
WordPress 7.0.1 is scoped strictly to bug fixes — no new features. Only tickets representing regressions introduced during the 7.0 development cycle, or issues deliberately deferred at the end of that cycle, will be included. The release is co-led by contributors cbravobernal, estelaris, masteradhoc, and jorbin. One known issue — affecting Classic Editor users who have added custom buttons to the post publishing panel — already has a fix available through the Hotfix plugin.
Four bug scrub sessions — collaborative reviews where contributors triage and prioritize open tickets — are scheduled before the release candidate drops, with a further scrub held between RC1 and the general release. The full timeline runs from mid-June through early July:
| Date / Time (UTC) | Event |
|---|---|
| Thursday, June 18 at 15:00 | Bug Scrub |
| Tuesday, June 23 at 15:00 | Bug Scrub |
| Thursday, June 25 at 20:00 | Bug Scrub; WordPress 7.0.2 milestone opens, some tickets may be deferred |
| Tuesday, June 30 at 10:00 | Bug Scrub |
| Wednesday, July 1 (time TBA) | WordPress 7.0.1 RC1 |
| Tuesday, July 7 at 15:00 | Bug Scrub |
| Thursday, July 9 | WordPress 7.0.1 General Release |
Exact times for the release candidate and the final release will be confirmed in the #7-0-release-leads Slack channel, depending on contributor availability. The June 25 bug scrub is also the point at which the WordPress 7.0.2 milestone will be opened, meaning any tickets that don’t make the 7.0.1 cut will begin rolling into the next patch.
Site owners who want to track progress can follow Trac report 4 or the 7.0.x editor tasks board on GitHub. Developers and testers who want to contribute can join bug scrub sessions in the #core Slack room, run their own scrubs using the team’s published guidelines, or help with translation — the team notes that some locales still have untranslated strings from the 7.0 release.
