Core bundles its own AI client in WordPress 7.0, so older AI Experiments builds fatal the moment you activate them. What is graduating out of experiment status, the LLM kill switch in Trac 64706, and how to load your own AI code without crashing.
WordPress 7.0 Beta 5 adds a Command Palette shortcut to the admin bar and closes more than 101 bugs. What the shortcut does, how to register your own commands with the API, and why I update beta sites with WP-CLI.
AI Experiments 0.5.0 requires WordPress 7.0, drops its bundled AI client for the one in core, and moves API keys to the Connectors screen. What that means if you are still on 6.9.
WordPress is looking for volunteers on the Twenty Twenty-Seven default theme, which ships with 7.2 in December 2026. What the work actually involves, why the schedule is tight, and how a core theme differs from any client build.
WordPress 7.0 Beta 3 keeps the AI client in core small and pushes the providers out to plugins: Anthropic, Google and OpenAI are on the repository already, with Ollama being prepped. Plus where the MCP adapter is going and what AI Experiments 0.5.0 drops.
WooCommerce 10.6 is mostly maintenance: SQL fixes in the admin, lazy loading on by default for the Product Image block, and two changes that can break custom breadcrumbs and headless Store API calls.
Beta 3, a silent Beta 4 next to 6.9.3, and Beta 5 due March 12. What real-time collaboration, the new Breadcrumb block filters and theme.json pseudo-elements mean for your custom code before the RCs land.
The release party is a Slack marathon that produces a hundred reports saying everything looks good and almost no usable coverage data. A proposal: structured JSON reports, identical Playground environments, and pairing contributors at WordCamp Asia.
WordPress 6.9.3 is a fast-follow fix for a 6.9.2 regression that blanked out sites whose themes returned stringable objects to template_include. Here is what broke, and what you need to update.
my.WordPress.net turns WordPress Playground into a workspace that survives a page reload. The site lives in browser storage instead of on a server, and Blueprints handle the setup. Clear your cache without a backup and it is gone.