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.
The latest dev chat turned into an argument over whether WordPress Core should require PHP’s filter extension. PHPMailer uses it today. Here is what that costs you on hosts that compiled PHP without it.
A WooCommerce site broke because its new host had no bcmath extension. The proposed filter for the required PHP extensions list in core would catch that kind of gap before checkout starts failing.
Twenty near-identical buttons in one design file cost me three hours per border-radius tweak. Component variants in Penpot fixed that, and DTCG tokens made the handoff to CSS boring, which is exactly what you want.
The RTX 30-series has no hardware FP8, so I packed four FP8 values into one FP32 container and unpacked them inside a Triton kernel. On a client’s 3080s that cut the memory bottleneck and ran about 3.3x faster.
A core update took a client’s checkout page down at 2 AM. Reading the release retrospectives and controlling minor auto-updates per environment is how I stopped that from happening again.
WooCommerce 10.4 makes the Interactivity API mini cart the default, lazy-loads two REST namespaces, and takes HPOS caching out of experimental. Here is what to test before you update.