The Core-AI team shipped v0.1.0 of the WordPress PHP AI Client SDK. It is a provider-agnostic Composer package you bundle into your own plugin, so swapping the LLM behind a feature stops being a refactor.
WordPress 6.9.1 is a maintenance-only release set for February 3, 2026, with bug scrubs running from January 20. These are the dates that matter, plus why I keep minor auto-updates off on sites with custom hooks.
WordPress now has WP-Bench, a benchmark that tests AI models on Core APIs, security patterns and block development. It runs the generated code in a real WordPress runtime instead of grading answers on paper.
Gutenberg 22.3 is the first clear look at the WordPress 7.0 developer features: combined grid controls, a dedicated Fonts screen, and PHP-only block registration. Here is what each one changes on a production site.
The January 2026 Dev Chat confirmed WordPress 7.0 will drop PHP 7.2 and 7.3. Here is what that frees up in core, where the filter extension argument stands, and how to get on the release squad.
WordPress Playground spent 2025 getting 42% faster and reaching 99% compatibility with the top 1,000 plugins. Here is what changed in Blueprints and database support, and why it now works for real testing.
WooCommerce 10.5 fixes two decoding bugs that broke Arabic, Persian and Chinese attribute names and values on variation writes. What changed, how to test it with cURL, and which old workarounds to pull out.
WordPress 7.0 drops PHP 7.2 and 7.3 support. What the new floor lets core use, where the filter extension debate stands, and how to check for the extension before it throws a fatal error.
The January 2026 core performance chat: speculative loading may default to moderate eagerness on cached sites, the admin view transitions PR is stuck on E2E failures, and modern image formats still have rough spots.
WordPress 7.0 drops PHP 7.2 and 7.3 in April 2026 and makes 7.4 the minimum. What that means for older sites, why the project is doing it, and why 8.x is the version you actually want.