The screenshots gallery on WordPress.org plugin pages now renders core Gallery and Image blocks with the standard lightbox, while the masonry part stayed out of core. Here is what shipped, why core turned the masonry down, and how I would build the same thing.
June was a loud month: WordPress 7.0 is out, React 19 got reverted, and media processing moved into the browser. Here’s how I split the roundup into what gets tested now on real sites and what gets filed for later.
Gutenberg shipped React 19 in 23.3.0, watched plugins that bundle React 18 crash in the editor, and rolled the runtime back in 23.3.2. Here is why bundling your own jsx-runtime caused it, and what I’d check on client sites before WordPress 7.1.
WordPress 7.1 wants your browser to resize uploads with libvips in WebAssembly, and the server to just store them. The gates are narrow, the fallback is silent, and media plugins that hook PHP have real testing to do before this ships.
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.
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.
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.
The WordCamp Asia committer notes are mostly process talk, but the SQLite paragraph reaches plugin authors first. What the notes settled, which schema habits break under SQLite, and what I’d test before core writes its support policy.
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.