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.
An AI assistant that can’t see your project turns every review into a copy-paste loop. What I’d build myself, what I’d leave to the official SDK, and where the sandbox boundary belongs when the root contains wp-config.php.
Most teams using AI on a WordPress site pay a hidden tax in copy, paste and rewritten prompts, and another SaaS rarely removes it. The fix, for me, is moving the prompt into your own code with wp_remote_post, WP-CLI, caching and a small model, so the workflow runs where the data already lives.
The WooCommerce monorepo watch build used to eat 24.4 GB of RAM before it was ready. The fix was not a faster compiler. It was deleting work nobody consumed, moving type checks to lint, and letting webpack bundle from source. Here are the four changes and the cold build regression they accepted.
The Core AI Team runs a table at WordCamp Europe’s Contributor Day on June 4. Before you go, two decisions matter: which environment you bring and where your model lives. This is the setup order I’d use, starting with one command the night before.
A hundred lines of Python, no vector database, and a real PDF. That is the baseline this author ships, with answers that cite exact lines. The part worth borrowing for WordPress work is the answer schema: typed JSON, verifiable quotes, and a null path that refuses to invent.
The WordPress version changelog stopped listing @wordpress package versions per release, and the versions page split in two. Here is where the package information lives now, what the split means for old links, and why the per-release notes are the part to watch.
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 shipping read-only abilities across Subscriptions, WooPayments, shipping and marketing extensions, and it published the agent skills used to build them. I’d skip the hype and use those skills on your own plugin: install, audit, register behind a version guard, then verify.
WordPress 7.0 shipped an AI Client, a Connectors API, and a Connectors screen, and left the actual features to plugins. Here is what that means for self-hosted sites, where provider keys should live, and what to test before enabling anything on production.