July 2026 marks the start of the WordPress 7.1 release cycle. The first beta version is set for July 15, followed by weekly releases, with the final version expected on August 19, 2026, coinciding with WordCamp US. Site owners should prepare for testing new features and updates that could impact their websites.
WordPress 7.1 Release Schedule
The timeline for WordPress 7.1 is crucial for site owners and developers. Key dates include:
- Beta 1: July 15
- Beta 2: July 22
- Beta 3: July 29
- Release Candidate 1: August 5
- Final Release: August 19, 2026
These dates provide a window for testing and ensuring compatibility with existing themes and plugins.
Updates and Fixes in WordPress 7.0.1
On July 9, 2026, WordPress 7.0.1 was released, addressing 13 bug fixes for both Core and Gutenberg. This maintenance update is essential for site stability and should be applied promptly to avoid issues before the 7.1 transition.
New Features in Gutenberg 23.5
Gutenberg 23.5, released on July 1, 2026, raises the minimum required WordPress version to 6.9 and introduces responsive styling features. Site owners should test these new capabilities to ensure their themes and plugins function correctly with the updated editor.
Preparing for Testing
With the upcoming changes in WordPress 7.1, site owners must actively test their plugins and themes against the new beta versions. This proactive approach will help identify compatibility issues early and ensure optimal performance after the final release.
Frequently Asked Questions
What is the release date for WordPress 7.1?
The final release of WordPress 7.1 is scheduled for August 19, 2026.
What changes are included in WordPress 7.0.1?
WordPress 7.0.1 includes 13 bug fixes for Core and Gutenberg, released on July 9, 2026.
What is the minimum required version for Gutenberg 23.5?
Gutenberg 23.5 raises the minimum required WordPress version to 6.9.
How can I test the new responsive styling features?
You can test the new responsive styling features in Gutenberg 23.5 by enabling the relevant options in the editor.