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 6.9.4 re-applies three security fixes that 6.9.2 and 6.9.3 left incomplete: PclZip path traversal, XXE in getID3, and a Notes authorization bypass. It also covers the WP-CLI commands I use to update core and check the files afterwards.
WordPress 7.0 adds a watch() function to the Interactivity API for side effects that do not belong to a single DOM element, and the router store now gets state.url from the server, so the undefined guards can go. Two navigation properties are deprecated along the way.
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.
Gutenberg 22.7 ships the Connectors API, turns real-time collaboration on by default, adds live previews for style variations, and puts phpMyAdmin in wp-env. Notes on what to test before you ship it.
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.