WordPress 7.0 Beta 1 puts real-time collaboration in core, adds a provider-agnostic WP AI Client on top of the Abilities API, and moves image resizing into the browser. Final release is set for April 9, 2026.
Core has to decide whether the WP AI Client merges into WordPress 7.0 before Beta 1 on February 19, 2026. My read on the Abilities API friction in ticket #64596 and what a provider-agnostic client changes in plugin code.
AI Experiments 0.3.0 moves the plugin’s AI features into the editor itself: an AI Summary block, image generation in the post sidebar, and alt text on request. The developer side gets strict typing in the Abilities Explorer and cleaner asset handling.
Notes from the recent AI Contributor meeting: a single Connectors screen for external service credentials, nested namespaces for Abilities, and whether any of it is ready in time for the WordPress 7.0 Beta 1 deadline.
From April 14, WooCommerce 10.7 ships with HPOS sync on read disabled. Custom code that edits orders through update_post_meta or raw SQL stops reaching the HPOS tables, so it needs moving to the CRUD API. There is a filter to buy time, but only that.
Notes from the WordPress 7.0 product review meeting with Matt Mullenweg: a CSS-level admin refresh, a customizable dashboard, real-time co-editing over a pluggable transport, the AI Client and its settings UI, and PHP-only block registration.
WooCommerce 10.5 moves the analytics import onto a schedule and processes orders in batches of 100. Notes on the new experimental caching flags, the wp_options autoload update, and what I would test on staging before shipping it.
WordPress 7.0 ships April 9, 2026, live from WordCamp Asia. Here are the release party dates in #core, from Beta 1 in February through the 24-hour code freeze, and what each phase is for.
WordPress 6.9.1 shipped, but the interesting decisions sit in the 7.0 roadmap: merging the WP AI Client into core, running libvips in worker threads, and realtime editing that your hosting may not survive.
The WP AI Client merge proposal for WordPress 7.0 raises three real problems: bundled third-party dependencies, flat versus nested ability namespaces, and an update settings ability that can write to the database.