WordPress 7.1 Beta: React 19 Returns, This Time It Sticks

WordPress 7.1 Beta 1 drops July 15. You have 35 days before the final release on August 19 — and the React 19 upgrade that crashed half the plugin ecosystem in June is back on the menu. This time there is a compatibility shim. There is also a hard deadline. If your plugin bundles its own React runtime, stop reading this and go enable the gutenberg-react-19 experimental flag instead.

React 19: The June Incident Was a Warning, Not an Exception

On June 3, Gutenberg 23.3 shipped with React 19. By June 5, it was reverted. In between, plugins that bundled their own copy of react/jsx-runtime — which describes most plugins built without relying on @wordpress/element — caused admin screens to white-screen and block editors to half-load. The only fix was to either downgrade Gutenberg or deactivate the offending plugin.

The core team did not retreat. They called the revert part of the plan. The next attempt — WordPress 7.1 — will include two things the June attempt lacked: a compatibility layer that prevents immediate crashes for already-released plugins, and an experimental gutenberg-react-19 flag in Gutenberg 23.4 that simulates exactly what production plugins will face when 7.1 ships. Compatibility polyfills log console warnings whenever a plugin hits a removed legacy internal. That testing window is open now. Ignoring it means finding out in August instead.

What React 19 removes is not subtle. ReactDOM.render(), hydrate(), and unmountComponentAtNode() are gone. findDOMNode() is gone. defaultProps on function components is gone. If any of these appear in your plugin or in a third-party dependency you have bundled, you will get failures — not warnings, failures.

Additionally, approximately 20 components in Gutenberg are hard-deprecating the __next40pxDefaultSize prop. The 40-pixel control size is now permanent. Layouts built around the old smaller default need reviewing before August. This is not optional housekeeping — it is a breaking change dressed as a deprecation.

WordPress 7.1 AI Features: Streaming Responses and Vector Embeddings

While the React 19 drama dominates the breaking-changes discussion, WordPress 7.1 is doing something more interesting on the AI side. The AI Client introduced in WordPress 7.0 gains two new primitives in 7.1: generation streaming and vector embeddings.

Streaming is what it sounds like — responses arrive token-by-token in real time instead of after a full generation wait. However, there is an important caveat: streaming ships in the PHP AI Client framework layer first, not natively in WordPress itself. Standard WordPress requests time out after 30 seconds, and streaming requires multi-minute connections. Developers and hosts get the underlying pipe; building the WordPress-level support comes later.

Vector embeddings are the bigger story. MySQL and MariaDB now support native vector storage, and WordPress 7.1 adds embeddings support to the AI Client to take advantage of this. An embedding is a numerical representation of text that encodes semantic meaning. With embeddings, a search for “how do I reset my password” correctly matches a page titled “Account recovery steps” despite sharing no keywords. That is semantic search — and it is now part of WordPress core infrastructure, available to any plugin pointing at OpenAI, Gemini, or Claude through the unified AI Client interface, with no external vector database required.

Furthermore, the new wp_knowledge custom post type completes the picture. It is a centralized repository for site-level editorial rules: brand voice guidelines, content standards, memory notes. It supports three default knowledge types (guideline, memory, note), ships with permissions, revisions, and REST routes at /wp/v2/knowledge, and is queryable by both editors and AI content generators. Store editorial standards there, and an AI-assisted writing tool can query them at generation time. The combination of streaming generation, vector embeddings, and a structured knowledge layer is, effectively, a RAG architecture built into a CMS running 43 percent of the web.

Plugin developers who have spent the past year wiring up per-plugin OpenAI wrappers and external Pinecone instances now have a native alternative. We covered the initial foundations of this in our earlier WordPress 7.1 roadmap post — what has changed since June is that the June incident proved the React 19 migration is real, and the AI Client details are now concrete enough to build on.

Other Breaking and Notable Changes in WordPress 7.1

Beyond React and AI, several changes in 7.1 will catch plugin and theme authors off guard.

All 330 icons in @wordpress/icons v15 now declare fill="currentColor". If you are styling icons using the CSS fill property, switch to color before August or your icon colors break silently. The @wordpress/reusable-blocks package is fully deprecated — all store actions and selectors now log warnings, and removal is coming. The admin bar returns by default in both the post editor and site editor; if your plugin places UI near the editor header, retest the layout. The editor now enforces iframing for block-based themes, meaning blocks must use Block API version 3. The useResizeCanvas() hook is deprecated as part of the responsive styling overhaul, though getDeviceType() and setDeviceType() remain functional.

WordPress 7.1 also adds Unicode email support — UTF-8 local parts, internationalized domains via Punycode, and a new WP_Email_Address class. If your plugin validates or stores email addresses, test is_email() and sanitize_email() against Unicode inputs now. Not later. Now.

What WordPress Developers Must Do Before August 19

Beta 1 is the testing window. The final release does not care if your plugin is ready. Here is the action list:

• Enable gutenberg-react-19 under Gutenberg → Experiments and audit every console warning
• Stop bundling React — use @wordpress/element and let core own the runtime
• Remove ReactDOM.render(), findDOMNode(), and defaultProps from function components
• Remove __next40pxDefaultSize and adjust layouts that relied on the smaller default size
• Switch icon tinting from CSS fill to the color property
• Retest any plugin UI that lives near the editor header (admin bar is back)
• Test Unicode email inputs if your plugin handles address validation or storage
• Migrate off @wordpress/reusable-blocks before warnings become errors

WordPress 7.1 is not a dramatic release on its face. The AI features are developer primitives, not end-user flourishes. The React 19 migration is an upgrade WordPress was always going to make. But the June incident proved that “always going to happen” and “everyone is ready” are different things. Beta 1 is the correction window. It closes August 19.