The 10.5.1 patch undoes the script check that left add to cart disabled on variable products, reverts the Divi shop page hooks that threw PHP warnings, and adds token validation to PayPal Standard shipping callbacks.
Gutenberg 22.5 brings custom CSS on individual block instances, aspect ratio control on wide and full alignments, and a List View that shows real item content. Notes on what each one changes day to day.
WordPress 7.0 makes the post editor always iframed, which breaks editor JavaScript that reaches for the global document. Also here: native viewport-based block visibility, per-instance custom CSS, and the Studio 1.7.0 CLI updates.
Notes from the February 4 contributor meeting on the WordPress AI Client merge into 7.0: why OpenAI, Google and Anthropic are moving out to separate plugins, why the off switch is a constant rather than a filter, and what MCP adapters mean for the Abilities API.
Notes on the WordPress 7.0 AI integration roadmap: the WP AI Client merge proposal, the GatherPress demo built on the Abilities API, how the native client compares to the MCP adapter, and what has to land before the February 19 Beta 1 deadline.
The WordPress Foundation, UIC and Automattic are running a paid micro-credential pilot called AI Leaders: 80 students in Illinois and Louisiana, a $1,000 stipend, and real WordPress AI work instead of prompt-writing exercises. Here is what that changes for hiring.
WooCommerce 10.5 was due on February 3, 2026 and did not ship. Removing the AccessiblePrivateMethods trait looked risky enough in testing that the team left it in, with a status update set for February 4 at 12pm UTC.
Freshly Pressed is back in the WordPress.com Reader, with people picking the posts instead of an engagement score. If you are self-hosted, that only helps once your Jetpack sync is actually working, so here is what to check.
The February 4, 2026 dev chat put client-side media on the road to WordPress 7.0: libvips compiled to WASM, running in a worker thread, with image resizing done in the visitor’s browser instead of on your server.
WordPress is testing Gutenberg Content Guidelines, a machine-readable place to keep brand voice, accessibility and image rules so plugins and AI tools can read them instead of guessing from a PDF nobody opens.