WordPress 7.0 Beta 3 ships 148 fixes and swaps the static AI provider list for the WP AI Client registry. Here is what changed in the connectors screen and how to test it on staging before the April 9 release.
WordPress 7.0 in Beta 3: RTC syncs over HTTP polling with Yjs, AI connectors give plugins one shared interface, and patterns default to content-only editing. Patch 6.9.2 before you touch any of it.
WordPress 7.0 Beta 2 adds one Connectors screen for AI providers and forces Block API v3 blocks into the iframed editor. Both change what your plugin code has to do before the April 9 release.
AI Experiments 0.4.0 puts prompt-based image generation in the Block Editor and the Media Library, and adds a Generate Review Notes pass for accessibility and readability. It also points at the WordPress AI rename in 0.5.0.
WordPress 7.0 supports :hover, :focus, :focus-visible and :active inside theme.json for blocks and their variations. What that replaces, how the JSON looks, and the limits worth knowing before you refactor.
Beta 2 landed on February 26th and Beta 3 is due March 5th. The parts that matter for developers: blocks you can register in PHP alone, an iframed editor that isolates your CSS, and the handbook back in sync with Gutenberg 22.6.
Mobile menus in WordPress 7.0 are template parts you edit in the Site Editor. This covers the navigation-overlay area, the theme.json registration, the close block you should add yourself, and the full-screen-only limit in this first release.
WordPress 7.0’s AI updates are heading into Beta 2. This post covers the pivot away from the Abilities API, the new Connector Screen, and the dependency issues in the AI Experiments plugin.
WordPress 7.0 brings real-time collaboration and AI connectors into core, but legacy PHP meta boxes turn into a compatibility bottleneck. This post covers the latest Dev Chat agenda and what to fix before Beta 2.
WooCommerce 10.6 ships March 10, 2026. It cuts checkout SQL queries with deferred transient deletion, batches admin options, and breaks three things worth patching first: Store API per_page, lazy-loaded images, and a null breadcrumb argument.