# What's New for Developers (July 2026) > [!question] Lingering Questions > - What specific feedback actually drove the Classic block reversal — forum threads, Trac comments, social posts? The article implies pushback but never names its source. > - Does the `wp_knowledge` CPT's REST API (`/wp/v2/knowledge`) carry any access scoping beyond standard capability checks, given it's likely built for AI-agent consumption? > - How many currently-published .org plugins would fail under the `gutenberg-react-19` flag, and is a compatibility-scan tool planned before React 19 becomes default? > [!tip] Article Ideas > - A consolidated "breaking changes in 7.1" table (change / affected API / action required / deadline) would serve this roundup's content better than its current prose-bullet scatter — could be a useful format to build once, then reuse each release cycle. > - Revisit this roundup after 7.1 ships (Aug 19, 2026) to compare the predicted breakage (icons, 40px defaults, React 19) against actual plugin-directory fallout. > [!link] Cross Reference > - [[3. Resources/Permanent Notes/Hiding Not Removing Deprecates a Legacy Feature Safely]] — same Classic-block episode, read from the deprecation-mechanics side rather than the reversal-under-pushback side > - [[3. Resources/Permanent Notes/Default-Off Feature Flags Decouple Shipping Speed From Production Risk]] — a contrasting risk-management move: the `gutenberg-react-19` flag ships opt-in specifically so incompatibilities surface before React 19 becomes the unconditional default > [!quote] Vocabulary > - **Core Abilities** — a WordPress core API surface exposing discrete, capability-checked actions (here, three new read-only ones) for programmatic/agent consumption > - **Blueprint v2** — an in-progress WordPress Playground compiler rewrite; explicitly flagged as not yet usable syntax ## Metadata - Source: [[3. Resources/Readwise/Articles/What's New for Developers (July 2026)]] - Published: 2026-07-10 · WordPress Developer Blog ## Author's thesis WordPress 7.1 enters its beta cycle (July 15 – Aug 19, 2026, timed to WordCamp US) carrying a large, mostly additive feature set — Core Abilities expansion, AI Client streaming/embeddings, Playground MCP support, layout/grid work — bundled with several real breaking changes (icon color inheritance, hard-deprecated 40px control default, experimental React 19 mode) that plugin and theme authors need to test against during the beta window, not after release. ## Key arguments (≤3) 1. **The 40px and icon-color changes are silent breakers.** ~20 `@wordpress/components` lose the `__next40pxDefaultSize` opt-in (40px becomes unconditional), and all 330 `@wordpress/icons` switch to `fill="currentColor"` — any CSS recoloring icons via `fill` directly stops working with no console warning tied to the CSS itself. 2. **Core reversed a forced-removal decision.** The plan to hide the Classic block from the inserter for 7.1 was walked back; the team's stated focus shifted to building better alternatives instead of forcing the change — the one clear "core changes course" moment in an otherwise forward-only roundup. 3. **"Test now, before it's forced" is the article's organizing logic.** The 7.1 beta schedule, two open Calls for Testing (Responsive Styling, Unicode email addresses), and the opt-in `gutenberg-react-19` flag are all framed as pre-default trial windows — a repeated flag-then-default rollout discipline visible across React 19, the 40px change, and speculative loading. ## Claim atoms ### WordPress 7.1 final release lands August 19, 2026 > [!quote] ID:rw_wpdev202607_01 > "Final release: August 19, 2026 (WordCamp US)" Where/why: "Highlights" section — sets the hard deadline for every compatibility-testing item in the roundup. ### Icons v15 makes fill a breaking change > [!quote] ID:rw_wpdev202607_02 > "All 330 icons in @wordpress/icons v15 declare fill=\"currentColor\", a breaking change." Where/why: "Icons Now Inherit Color" — any plugin/theme CSS targeting icon `fill` directly silently stops recoloring icons; the fix is CSS `color`. ### Classic block stays after plan reversal > [!quote] ID:rw_wpdev202607_03 > "The original plan to hide the Classic block from the inserter for 7.1 was reverted." Where/why: concrete instance of core reversing an announced forced-UX-change decision — rare enough in this roundup's structure to flag distinctly. ### Unicode email support closes an 11-year-old ticket > [!quote] ID:rw_wpdev202607_04 > "The Unicode email proposal merged into trunk, closing a ticket opened in 2015." Where/why: illustrates how long some core proposals take from ticket-open to merge — useful context for expectations on the other open merge proposals in the same roundup. ## Permanent candidates - **Forced UX changes get reverted under visible pushback** — strongest candidate; generalizes past WordPress to any project shipping a forced-removal change without a ready replacement. Promoted below. ## Processing checklist - [x] Pull claim atoms and permanent candidate from the existing deep-read notes - [x] Connect into a relevant MOC - [ ] Revisit after 7.1 ships (2026-08-19) to check predicted vs. actual breakage ## Links - [[3. Resources/MOCs/Open Source Governance MOC]] — the Classic block reversal and the two open merge proposals (Core Abilities, `wp_knowledge`) are live instances of how WordPress core governance handles contested UX and API-surface decisions