Hiding a block used to mean display: none and a browser that still downloaded every asset. WordPress 6.9 leaves hidden blocks out of the rendered HTML, and a short filter stops clients from hiding your structural containers.
A magazine site moving off an emoji subdomain came apart under wp search-replace. WordPress Importer 0.9.5 rewrites URLs during the import instead, using the block markup parsers in core to tell a real URL from a lookalike string.
Core heading styles used to outrank theme CSS inside the editor, which is how a stylesheet ends up full of !important. WordPress 6.9 changes how those styles are injected, and RC3 is out now for testing.
WordPress 6.9 ships live on stage during State of the Word on December 2. The timeline behind it, from the dry run 26 hours out to the T-30m handoff, is worth borrowing for your own launches.
WordPress 6.9 deprecates the core-data media entity, lets setAttributes take an updater function, and moves SelectControl class names to the root element. Each one can break an existing custom block.
An official WordPress GitHub repo is not a support promise. Roughly 20 repos were archived across the WordPress and bbPress orgs, which is a good reason to go looking for orphaned code in the sites you maintain.
A tiny patch to a custom gateway plugin broke checkout for about 15% of one store’s customers. Release Confirmation, tracked in #8009-meta, holds auto-updates back for 24 hours so a mistake like that stays small.
I once spent three weeks bolting a permissions layer onto custom REST endpoints so an AI agent could not wreck a client’s product catalog. The Abilities API landing in WordPress 6.9 is the standard that job was missing.
A client wanted their block plugin hosted under the WordPress GitHub organization and found the path opaque. Here are the actual criteria: community ownership, a sponsoring Make team, more than one maintainer, and what happens when maintenance stops.
Plugins have always exposed their features however they liked, so integration meant writing a wrapper per plugin and repairing it after every update. The Abilities API in WordPress 6.9 replaces that with one registration format.