Gutenberg 23.3 quietly moves the editor to React 19, and that is the item most likely to break a custom plugin. This post covers which legacy patterns were removed, how per-block responsive styles affect themes, and what stays behind an experiment flag.
WooCommerce 10.9 shipped an experimental dual API: PHP classes that generate a GraphQL API. Here is how it stacks up against the REST and Store APIs, what it means for plugin developers, and which surface I would put under a real integration today.
WooCommerce is removing the block-based product editor beta from core in 11.0, due July 28. Product data is untouched and stores fall back to the classic editor. Here is what I’d check on a store, and what extension code needs to change before the removal lands.
WordPress wants real-world testers for collaborative editing, and the setup is a staging clone, the latest Gutenberg plugin, and a toggle under Settings, Writing. Here is my checklist for what breaks first and where to report it.
WordPress 7.1 is targeting React 19, and the npm packages are no longer tagged per version. Here is how I decide between core’s React and bundling my own, plus the checks I run before a major upgrade.
Custom media queries let you name a breakpoint once and use it everywhere, but native @custom-media support is still limited. This is how I compare the browser rule against a PostCSS build step before putting either on a WordPress or WooCommerce site.
The WordPress AI plugin is moving toward encrypted API keys and slowing to a monthly release cadence, both before WordPress 7.1 Beta 1 in July. This is how I’d audit client sites now, and why the Connectors field registry matters for self-hosted models.
The week after WordPress 7.0 shipped, the dev chat agenda quietly listed the field guide, three dev notes, a PHP clarification and unicode email support. I run the same four-pass triage on every agenda like this before touching a client site. This is the checklist.
WordPress planned React 19 for 7.1, then moved it to a Gutenberg experiment. The bigger risk is plugins that bundle their own React, so check your builds and test a store on staging before core ships it.
WordPress Guidelines keeps agent memory, skills and instructions in an ordinary custom post type, and it’s headed for Core. Here’s what that means for plugins with their own memory stores, which permissions to test first, and when a separate table still makes sense.