WordPress 7.0 changes how the iframed editor decides which posts get isolated CSS, checking blocks actually used in a post rather than every block registered on the site. Legacy blocks still work, but the push toward Block API version 3 is real.
WordPress.com built its new AI Assistant directly into the block editor and Media Library. It edits blocks and generates images with Google’s Gemini models, though full layout control needs a Block Theme.
The WordPress 7.0 collaboration prototype polls up to four times a second, and every poll wipes the object cache for the post it touches. Here is what Ticket #64696 found and why core is getting its first new table since 2015.
Amy Kamala and Jb Audras take over as WordPress core team reps for 2026. The job is administrative: run Dev Chat, move updates between teams, keep the release cycle predictable. No vote was needed this year.
WordPress 6.7 added PluginPreviewMenuItem, a Slot/Fill point in the editor Preview dropdown. This walks through enqueuing the assets, registering the menu item, and reading unsaved post data with useSelect for a social card preview.
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.
WooCommerce 10.5.2 reverts the change that left the Add to Cart button disabled on variable products when a theme or plugin altered how the variation scripts load. What went wrong, and the WP-CLI steps to update without stale variation data.
WooCommerce 10.6 stops accepting per_page=0 on Store API product and review requests, so those calls start returning 400 errors. How to move to batched requests, and the rest_endpoints filter to fall back on if you cannot refactor yet.
WordPress 7.0 Beta 1 slipped a day after unit tests failed in the REST autosave controller and Gutenberg’s real-time collaboration work. Why a broken autosave is worth delaying a release for, and where to follow the fix.
WordPress Core added an experimental wp-env runtime that runs PHP and SQLite through WebAssembly, so a full environment starts in seconds without Docker. Notes on the npx flag, the SQLite tradeoff, and the limits that still send me back to containers.