{"id":6232,"date":"2026-07-10T14:17:56","date_gmt":"2026-07-10T14:17:56","guid":{"rendered":"https:\/\/developer.wordpress.org\/news\/?p=6232"},"modified":"2026-07-10T14:39:18","modified_gmt":"2026-07-10T14:39:18","slug":"whats-new-for-developers-july-2026","status":"publish","type":"post","link":"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/","title":{"rendered":"What&#8217;s new for developers (July 2026)"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">July is the month the WordPress 7.1 cycle gets real. Beta 1 lands on July 15, betas follow weekly through the end of the month, and the final release is scheduled for August 19, 2026, timed with WordCamp US. If June was about wrapping up WordPress 7.0, July is about deciding what you need to test before 7.1 locks in.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Meanwhile, <a href=\"https:\/\/wordpress.org\/news\/2026\/07\/wordpress-7-0-1-maintenance-release\/\">WordPress 7.0.1 was released on July 9<\/a>. It <a href=\"https:\/\/make.wordpress.org\/core\/2026\/07\/01\/wordpress-7-0-1-rc1-is-now-available\/\">bundles 13 Core tickets and 13 Gutenberg fixes<\/a>, all bug-fix only.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On the plugin side, Gutenberg <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/17\/whats-new-in-gutenberg-23-3-03-jun-2\">23.4<\/a> (June 17) and <a href=\"https:\/\/make.wordpress.org\/core\/2026\/07\/01\/whats-new-in-gutenberg-23-5-july-1-2026\/\">23.5<\/a> (July 1) both shipped in the window. Note that Gutenberg 23.5 raises the plugin&#8217;s minimum required WordPress version to 6.9.As usual, when testing features mentioned in these What&#8217;s new? posts, ensure that you&#8217;re running the latest version of WordPress and the latest version of the Gutenberg plugin. You can also test the latest updates via <a href=\"https:\/\/playground.wordpress.net\/\">Playground<\/a>.<\/p>\n\n\n\n<div class=\"wp-block-group has-light-grey-2-background-color has-background is-layout-flow wp-block-group-is-layout-flow\" style=\"border-radius:2px;margin-top:var(--wp--preset--spacing--30);margin-bottom:var(--wp--preset--spacing--30);padding-top:var(--wp--preset--spacing--30);padding-right:var(--wp--preset--spacing--30);padding-bottom:var(--wp--preset--spacing--30);padding-left:var(--wp--preset--spacing--30)\">\n<p class=\"has-large-font-size wp-block-paragraph\" style=\"font-style:normal;font-weight:600;line-height:1\">Table of Contents<\/p>\n\n\n\n<nav aria-label=\"Table of Contents\" class=\"wp-block-table-of-contents\"><ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#highlights\">Highlights<\/a><ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#wordpress-7-1-mark-your-calendars\">WordPress 7.1: mark your calendars<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#responsive-styling-is-ready-for-testing\">Responsive styling is ready for testing<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#merge-proposal-expanding-core-abilities\">Merge proposal: expanding Core Abilities<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#merge-proposal-guidelines-built-on-knowledge\">Merge proposal: Guidelines built on Knowledge<\/a><\/li><\/ol><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#plugins-tools\">Plugins &amp; Tools<\/a><ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#react-19-test-your-plugins-now\">React 19: test your plugins now<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#components-drop-the-40px-opt-in-prop\">Components drop the 40px opt-in prop<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#icons-now-inherit-color-and-the-icons-api-takes-shape\">Icons now inherit color, and the Icons API takes shape<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#unicode-email-addresses-call-for-testing\">Unicode email addresses: call for testing<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#classic-block-status-in-wordpress-7-1\">Classic block status in WordPress 7.1<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#ai-client-streaming-and-embeddings-coming-in-7-1\">AI Client: streaming and embeddings coming in 7.1<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#package-level-changes-worth-a-changelog-read\">Package-level changes worth a changelog read<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#wordpress-studio-now-available-on-linux\">WordPress Studio now available on Linux<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#media-pipeline-follow-ups-and-the-return-of-infinite-scrolling\">Media: pipeline follow-ups and the return of infinite scrolling<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#plugin-directory-screenshot-galleries-rebuilt\">Plugin Directory screenshot galleries rebuilt<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#performance-what-to-watch-for-7-1\">Performance: what to watch for 7.1<\/a><\/li><\/ol><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#themes\">Themes<\/a><ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#the-admin-bar-returns-to-the-post-and-site-editors\">The admin bar returns to the post and site editors<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#layout-real-fixed-widths-and-auto-fit-grids\">Layout: real fixed widths and auto-fit grids<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#block-bindings-expand-to-list-items-and-nested-content\">Block Bindings expand to List Items and nested content<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#new-extensibility-surfaces-for-block-variations\">New extensibility surfaces for block variations<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#more-theme-facing-block-updates\">More theme-facing block updates<\/a><\/li><\/ol><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#playground\">Playground<\/a><ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#blueprint-steps-you-can-use-today\">Blueprint steps you can use today<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#mcp-meets-the-abilities-api\">MCP meets the Abilities API<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#personal-playground-remote-access-over-webrtc\">Personal Playground: remote access over WebRTC<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#blueprint-v2-is-coming-together\">Blueprint v2 is coming together<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#user-facing-changes\">User-facing changes<\/a><\/li><\/ol><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#resources\">Resources<\/a><ol><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#developer-blog\">Developer Blog<\/a><\/li><li><a class=\"wp-block-table-of-contents__entry\" href=\"https:\/\/developer.wordpress.org\/news\/2026\/07\/whats-new-for-developers-july-2026\/#general\">General<\/a><\/li><\/ol><\/li><\/ol><\/nav>\n<\/div>\n\n\n\n<h2 id=\"highlights\" class=\"wp-block-heading\">Highlights<\/h2>\n\n\n\n<h3 id=\"wordpress-7-1-mark-your-calendars\" class=\"wp-block-heading\">WordPress 7.1: mark your calendars<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The 7.1 cycle now has a <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/17\/announcing-the-wordpress-7-1-release-squad\">release squad<\/a>, a <a href=\"https:\/\/make.wordpress.org\/core\/2026\/07\/03\/wordpress-7-1-release-party-schedule\/\">release party schedule<\/a>, and a <a href=\"https:\/\/make.wordpress.org\/core\/2026\/07\/03\/bug-scrub-schedule-for-wordpress-7-1\/\">bug scrub schedule<\/a>.\u00a0<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The key dates:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Beta 1 on July 15<\/li>\n\n\n\n<li>Beta 2 on July 22<\/li>\n\n\n\n<li>Beta 3 on July 29<\/li>\n\n\n\n<li>Release Candidate 1 on August 5<\/li>\n\n\n\n<li>Final release on August 19, 2026, during WordCamp US.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/19\/roadmap-to-7-1\/\">Roadmap to 7.1<\/a> is the post to read closely. Beyond the items detailed below, it lists <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/issues\/38277\">pseudo-state styling<\/a>, new <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/issues\/77421\">Playlist<\/a>, <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/issues\/42229\">Table of Contents<\/a>, and <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/issues\/73230\">Tabs<\/a> blocks, an <a href=\"https:\/\/make.wordpress.org\/core\/2026\/02\/24\/iframed-editor-changes-in-wordpress-7-0\/\">enforced iframed editor for block themes<\/a>, and a change that moves the <a href=\"https:\/\/core.trac.wordpress.org\/ticket\/64066\">speculative loading default from conservative to moderate<\/a> when caching is detected.Beta 1 arrives just days after this post is published. If you maintain plugins or themes, the next few weeks are the window to influence what ships and to catch compatibility issues while they are still cheap to fix.<\/p>\n\n\n\n<h3 id=\"responsive-styling-is-ready-for-testing\" class=\"wp-block-heading\">Responsive styling is ready for testing<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Responsive style states have appeared in these roundups for months as work in progress. That changed on July 3 with an official <a href=\"https:\/\/make.wordpress.org\/test\/2026\/07\/03\/call-for-testing-responsive-styling\/\">Call for Testing: Responsive Styling<\/a>. You can now style blocks per viewport directly in the editor, and Gutenberg 23.5 replaces the fixed desktop\/tablet\/mobile preview toggle with a <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/75121\">unified, freely resizable device preview<\/a>. <\/p>\n\n\n\n<figure data-wp-context=\"{&quot;imageId&quot;:&quot;6a63a311481ce&quot;}\" data-wp-interactive=\"core\/image\" data-wp-key=\"6a63a311481ce\" class=\"wp-block-image alignwide size-large wp-lightbox-container\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"762\" data-wp-class--hide=\"state.isContentHidden\" data-wp-class--show=\"state.isContentVisible\" data-wp-init=\"callbacks.setButtonStyles\" data-wp-on--click=\"actions.showLightbox\" data-wp-on--load=\"callbacks.setButtonStyles\" data-wp-on--pointerdown=\"actions.preloadImage\" data-wp-on--pointerenter=\"actions.preloadImageWithDelay\" data-wp-on--pointerleave=\"actions.cancelPreload\" data-wp-on-window--resize=\"callbacks.setButtonStyles\" src=\"https:\/\/developer.wordpress.org\/news\/files\/2026\/07\/responsive-styling-1024x762.png\" alt=\"The WordPress block editor showing the responsive styling controls.\" class=\"wp-image-6235\" srcset=\"https:\/\/developer.wordpress.org\/news\/files\/2026\/07\/responsive-styling-1024x762.png 1024w, https:\/\/developer.wordpress.org\/news\/files\/2026\/07\/responsive-styling-300x223.png 300w, https:\/\/developer.wordpress.org\/news\/files\/2026\/07\/responsive-styling-768x571.png 768w, https:\/\/developer.wordpress.org\/news\/files\/2026\/07\/responsive-styling-1536x1143.png 1536w, https:\/\/developer.wordpress.org\/news\/files\/2026\/07\/responsive-styling-2048x1523.png 2048w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><button\n\t\t\tclass=\"lightbox-trigger\"\n\t\t\ttype=\"button\"\n\t\t\taria-haspopup=\"dialog\"\n\t\t\tdata-wp-bind--aria-label=\"state.thisImage.triggerButtonAriaLabel\"\n\t\t\tdata-wp-init=\"callbacks.initTriggerButton\"\n\t\t\tdata-wp-on--click=\"actions.showLightbox\"\n\t\t\tdata-wp-style--right=\"state.thisImage.buttonRight\"\n\t\t\tdata-wp-style--top=\"state.thisImage.buttonTop\"\n\t\t>\n\t\t\t<svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"12\" height=\"12\" fill=\"none\" viewBox=\"0 0 12 12\">\n\t\t\t\t<path fill=\"#fff\" d=\"M2 0a2 2 0 0 0-2 2v2h1.5V2a.5.5 0 0 1 .5-.5h2V0H2Zm2 10.5H2a.5.5 0 0 1-.5-.5V8H0v2a2 2 0 0 0 2 2h2v-1.5ZM8 12v-1.5h2a.5.5 0 0 0 .5-.5V8H12v2a2 2 0 0 1-2 2H8Zm2-12a2 2 0 0 1 2 2v2h-1.5V2a.5.5 0 0 0-.5-.5H8V0h2Z\" \/>\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">There are real developer implications here. The <code>useResizeCanvas()<\/code> <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/75121\">hook is deprecated and no longer operational<\/a>, while <code>getDeviceType()<\/code> and <code>setDeviceType()<\/code> continue to work. Blocks that use standard block supports get responsive styles for free; blocks with custom controls do not. On the Core side, the <a href=\"https:\/\/core.trac.wordpress.org\/changeset\/62559\"><code>@<\/code> prefix syntax for responsive style states<\/a> has been adopted, and <a href=\"https:\/\/core.trac.wordpress.org\/changeset\/62513\">aspect-ratio<\/a> and <a href=\"https:\/\/core.trac.wordpress.org\/changeset\/62514\">flex-alignment<\/a> controls now work inside viewport states. If your blocks ship custom style controls, or your themes lean on <code>theme.json<\/code> presets, run through the call for testing and report what breaks.<\/p>\n\n\n\n<h3 id=\"merge-proposal-expanding-core-abilities\" class=\"wp-block-heading\">Merge proposal: expanding Core Abilities<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The Abilities API <a href=\"https:\/\/make.wordpress.org\/core\/2025\/11\/10\/abilities-api-in-wordpress-6-9\/\">shipped as infrastructure in WordPress 6.9<\/a>, and a new <a href=\"https:\/\/make.wordpress.org\/core\/2026\/07\/02\/merge-proposal-expanding-wordpress-core-abilities\/\">merge proposal<\/a> aims to add the first practical abilities to Core: <a href=\"https:\/\/core.trac.wordpress.org\/ticket\/64605\"><code>core\/read-settings<\/code><\/a>, <a href=\"https:\/\/core.trac.wordpress.org\/ticket\/64606\"><code>core\/read-content<\/code><\/a>, and <a href=\"https:\/\/core.trac.wordpress.org\/ticket\/64657\"><code>core\/read-users<\/code><\/a>. All three are read-only and built on existing capability checks, with <code>core\/manage-*<\/code> abilities planned for future releases.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hardening work continued alongside the proposal: ability filtering was refined and <a href=\"https:\/\/core.trac.wordpress.org\/changeset\/62548\"><code>meta<\/code> is now exposed over REST<\/a>, JSON Schema helpers were <a href=\"https:\/\/core.trac.wordpress.org\/changeset\/62549\">consolidated for reuse<\/a>, and the JavaScript packages gained <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79555\">URI schema format support<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you are building AI or automation features against the Abilities API, this proposal defines the first Core-provided abilities your code will be able to rely on. Feedback is open now.<\/p>\n\n\n\n<h3 id=\"merge-proposal-guidelines-built-on-knowledge\" class=\"wp-block-heading\">Merge proposal: Guidelines built on Knowledge<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The Guidelines experiment covered in earlier roundups has grown into a broader <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/22\/merge-proposal-guidelines-built-on-knowledge\/\">merge proposal for WordPress<\/a>. It introduces a <code>wp_knowledge<\/code> custom post type \u2014 a single place to store site knowledge, with permissions and revisions built in. It ships with three knowledge types (<code>guideline<\/code>, <code>memory<\/code>, and <code>note<\/code>), and a filter lets you register your own.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The proposal includes REST routes at <code>\/wp\/v2\/knowledge<\/code> and dedicated <code>*_knowledge_item<\/code> capabilities, and it is designed to have zero footprint on sites that never use it. To make 7.1, it needs to land by Beta 1 on July 15, so check the proposal&#8217;s status when you read this.<\/p>\n\n\n\n<h2 id=\"plugins-tools\" class=\"wp-block-heading\">Plugins &amp; Tools<\/h2>\n\n\n\n<h3 id=\"react-19-test-your-plugins-now\" class=\"wp-block-heading\">React 19: test your plugins now<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">June&#8217;s roundup covered the temporary revert of the React 19 upgrade. The action item has now changed from &#8220;watch&#8221; to &#8220;test.&#8221; Gutenberg 23.4 ships an experimental <code>gutenberg-react-19 <\/code>flag that <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79077\">swaps the React 18 bundles for React 19 at runtime<\/a>, simulating exactly what published plugins will face when WordPress makes the jump. Compatibility polyfills <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79624\">log console warnings<\/a> whenever a plugin hits a removed legacy internal.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If your plugin ships compiled JSX, uses <code>@wordpress\/element<\/code>, or touches editor internals, enable the flag under Gutenberg&#8217;s Experiments screen and watch the console. Every warning you fix now is a support ticket you avoid in August.<\/p>\n\n\n\n<h3 id=\"components-drop-the-40px-opt-in-prop\" class=\"wp-block-heading\">Components drop the 40px opt-in prop<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The biggest extender-facing change in the window is a coordinated hard-deprecation wave across <code>@wordpress\/components<\/code>. Starting with <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79386\">TextControl<\/a> on June 23 and continuing through roughly 20 components \u2014 including <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79419\">BoxControl<\/a>, <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79418\">BorderControl<\/a>, <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79481\">FontSizePicker<\/a>, <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79590\">RangeControl<\/a>, <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79636\">ComboboxControl<\/a>, <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79656\">ToggleGroupControl<\/a>, <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79721\">UnitControl<\/a>, <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79720\">FormTokenField<\/a>, and <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79796\">CustomSelectControl<\/a> \u2014 the <code>__next40pxDefaultSize<\/code> prop is hard-deprecated for WordPress 7.1.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The 40px control size becomes the permanent default, and the prop becomes a no-op. If your plugin UI passes <code>__next40pxDefaultSize<\/code> today, it will keep working, but expect deprecation warnings; if your UI relied on the old smaller default without the prop, review your layouts against the new sizing.<\/p>\n\n\n\n<h3 id=\"icons-now-inherit-color-and-the-icons-api-takes-shape\" class=\"wp-block-heading\">Icons now inherit color, and the Icons API takes shape<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">All 330 icons in <code>@wordpress\/icons<\/code> v15 now declare <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79320\"><code>fill=\"currentColor\"<\/code><\/a>, a breaking change for anyone styling icons with CSS. Tint icons with the CSS <code>color<\/code> property instead of <code>fill<\/code> going forward.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This lands amid steady buildout of the Icons API headed for WordPress 7.1: a new <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79686\"><code>wp\/v2\/icon-collections<\/code> REST endpoint<\/a>, <a href=\"https:\/\/core.trac.wordpress.org\/changeset\/62551\">label-based search in <code>WP_Icons_Registry<\/code>,<\/a> and <a href=\"https:\/\/core.trac.wordpress.org\/changeset\/62515\">stricter slug validation<\/a>. The <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/19\/roadmap-to-7-1\/\">roadmap<\/a> confirms <code>register_icon()<\/code> and <code>unregister_icon() <\/code>are planned for 7.1.<\/p>\n\n\n\n<h3 id=\"unicode-email-addresses-call-for-testing\" class=\"wp-block-heading\">Unicode email addresses: call for testing<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">June&#8217;s roundup flagged the Unicode email proposal as open for feedback. It has since merged into trunk, closing a ticket <a href=\"https:\/\/core.trac.wordpress.org\/ticket\/31992\">opened in 2015<\/a>, and there is now an official <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/10\/call-for-testing-unicode-email-addresses\/\">call for testing<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress now accepts UTF-8 local parts on sites with `utf8mb4` database support, handles internationalized domains via Punycode, and introduces a new <code>WP_Email_Address<\/code> class. If your plugin validates, stores, or compares email addresses \u2014 especially through <code>is_email()<\/code> or <code>sanitize_email()<\/code> \u2014 test against Unicode addresses now. The behavior can be disabled with a filter if needed.<\/p>\n\n\n\n<h3 id=\"classic-block-status-in-wordpress-7-1\" class=\"wp-block-heading\">Classic block status in WordPress 7.1<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Originally, there was a <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/23\/hiding-the-classic-block-from-the-inserter-in-wordpress-7-1\/\">plan to hide the Classic block from the inserter for 7.1<\/a>. This <a href=\"https:\/\/make.wordpress.org\/core\/2026\/07\/07\/the-classic-block-stays-in-the-inserter-for-wordpress-7-1\/\">decision has been reverted<\/a> and the Classic block will remain in WordPress for the foreseeable future and instead focus on creating experiences that users will choose instead of being forced to use.<\/p>\n\n\n\n<h3 id=\"ai-client-streaming-and-embeddings-coming-in-7-1\" class=\"wp-block-heading\">AI Client: streaming and embeddings coming in 7.1<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The AI team published a look at <a href=\"https:\/\/make.wordpress.org\/ai\/2026\/06\/19\/whats-coming-to-the-ai-client-in-wp-7-1\/\">what&#8217;s coming to the AI Client in WordPress 7.1<\/a>: streaming for generation responses and embeddings support for semantic and vector search. The focus remains on primitives for plugin developers rather than user-facing AI features.<\/p>\n\n\n\n<h3 id=\"package-level-changes-worth-a-changelog-read\" class=\"wp-block-heading\">Package-level changes worth a changelog read<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Several changes affect anyone consuming <code>@wordpress\/*<\/code> packages directly:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#8211; The <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79805\"><code>@wordpress\/reusable-blocks<\/code> package is deprecated<\/a>. All <code>core\/reusable-blocks<\/code> store actions and selectors, plus <code>ReusableBlocksMenuItems<\/code>, now log deprecation warnings, and the package is on a path to becoming a no-op. This has been milestoned for\u00a0 Gutenberg 23.6 whose release date has been moved to July 22nd.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#8211; A <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79095\">dependency-surface cleanup<\/a> fixed published dependencies across roughly 30 packages, made <code>@types\/react<\/code> an optional peer dependency, and fixed a <code>rememo<\/code> type leak.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">One warning for block developers: the experimental Tabs block <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79337\">removed its public <code>core\/tabs <\/code>store<\/a> as part of pre-stabilization cleanup. Do not build against it \u2014 the block is on the 7.1 roadmap, and its internals are still shifting.<\/p>\n\n\n\n<h3 id=\"wordpress-studio-now-available-on-linux\" class=\"wp-block-heading\">WordPress Studio now available on Linux<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/developer.wordpress.com\/studio\/\">WordPress Studio<\/a> saw some big releases the the last month. <a href=\"https:\/\/github.com\/Automattic\/studio\/releases\/tag\/v1.10.0\">Version 1.10<\/a> added Linux support and 1<a href=\"https:\/\/github.com\/Automattic\/studio\/releases\/tag\/v1.11.0\">.11.0<\/a> added Studio Code, WordPress.com&#8217;s agentic development tool, to the desktop app. It requires a WordPress.com to use, but usage is free during the beta phase.<\/p>\n\n\n\n<h3 id=\"media-pipeline-follow-ups-and-the-return-of-infinite-scrolling\" class=\"wp-block-heading\">Media: pipeline follow-ups and the return of infinite scrolling<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The client-side media processing work covered in June kept moving on the server side: GIF uploads can <a href=\"https:\/\/core.trac.wordpress.org\/changeset\/62623\">now generate video companion files<\/a>, HEIC and HEIF uploads are <a href=\"https:\/\/core.trac.wordpress.org\/changeset\/62616\">accepted even without server-side editor support<\/a>, and the REST attachment endpoint gained <a href=\"https:\/\/core.trac.wordpress.org\/changeset\/62617\">output format, progressive rendering, and quality fields<\/a>. <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/17\/whats-new-in-gutenberg-23-3-03-jun-2\/\">Gutenberg 23.4<\/a> added offline-resilient upload queues and preserves Ultra HDR gain maps when transcoding.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Separately, the Media Library is getting <a href=\"https:\/\/core.trac.wordpress.org\/ticket\/65564\">infinite scrolling back<\/a>, reversing a removal that dates to WordPress 5.8 \u2014 this time with a user opt-out option.<\/p>\n\n\n\n<h3 id=\"plugin-directory-screenshot-galleries-rebuilt\" class=\"wp-block-heading\">Plugin Directory screenshot galleries rebuilt<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The Plugin Directory <a href=\"https:\/\/make.wordpress.org\/meta\/2026\/06\/10\/plugin-directory-screenshots-gallery-update\/)\">rebuilt its screenshot galleries<\/a> using the core Gallery and Image blocks with lightbox support, an adaptive layout, and no more cropped previews. If you maintain a plugin listing, take a minute to check how your screenshots render now.<\/p>\n\n\n\n<h3 id=\"performance-what-to-watch-for-7-1\" class=\"wp-block-heading\">Performance: what to watch for 7.1<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The performance team&#8217;s 7.1 priorities, per recent <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/30\/performance-chat-summary-30-june-2026\/\">performance chat summaries<\/a>, are frontend View Transitions and Enhanced Responsive Images as feature plugins, plus <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/16\/performance-chat-summary-16-june-2026\/\">groundwork for a libvips-based image editor<\/a> in Core. And per the <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/19\/roadmap-to-7-1\/\">roadmap<\/a>, the <a href=\"https:\/\/core.trac.wordpress.org\/ticket\/64066\">speculative loading default<\/a> moves from conservative to moderate when a caching solution is detected.<\/p>\n\n\n\n<h2 id=\"themes\" class=\"wp-block-heading\">Themes<\/h2>\n\n\n\n<h3 id=\"the-admin-bar-returns-to-the-post-and-site-editors\" class=\"wp-block-heading\">The admin bar returns to the post and site editors<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Graduating from the omnibar experiment, the <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79197\">admin bar now shows by default<\/a> in both the post and site editors, and the W-logo corner has been replaced with a back button. This is headed to WordPress 7.1.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If your plugin injects UI near the editor header, retest your layout. Related cleanup moved the Gutenberg Experiments screen under Settings and <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79456\">removed the top-level Gutenberg admin menu<\/a>.<\/p>\n\n\n\n<h3 id=\"layout-real-fixed-widths-and-auto-fit-grids\" class=\"wp-block-heading\">Layout: real fixed widths and auto-fit grids<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Two layout changes give theme authors more precise control. Flex children with a &#8220;fixed&#8221; width are now <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79073\">truly fixed<\/a> via <code>flex-shrink: 0<\/code>, with the old squishable behavior renamed &#8220;Max width.&#8221; And grid layouts gained a <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79356\">&#8220;fill available space&#8221; toggle<\/a> (releasing July 22nd with Gutenberg 23.6) that switches column behavior from <code>auto-fill<\/code> to <code>auto-fit<\/code> through a new <code>autoFit<\/code> layout property. Both changes have landed in Core for 7.1, alongside flex <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79426\">vertical alignment controls<\/a> in the inspector.\u00a0<\/p>\n\n\n\n<h3 id=\"block-bindings-expand-to-list-items-and-nested-content\" class=\"wp-block-heading\">Block Bindings expand to List Items and nested content<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Block Bindings gained <a href=\"https:\/\/core.trac.wordpress.org\/ticket\/65406\">List Item block support<\/a> in Core, and bound rich text now <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79346\">preserves nested inner blocks<\/a> instead of flattening them. The 7.1 roadmap lists bindings for list items and inner blocks as a headline item, so expect more here before Beta 1.<\/p>\n\n\n\n<h3 id=\"new-extensibility-surfaces-for-block-variations\" class=\"wp-block-heading\">New extensibility surfaces for block variations<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Two quieter changes open up new patterns. Custom HTML block variations can now ship <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79659\"><code>innerContent<\/code><\/a>, so <code>registerBlockVariation( 'core\/html', { innerContent: [ \/* ... *\/ ] } )<\/code> lets you distribute static markup with editable slots. And block transforms <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/78713\">can now target specific variations<\/a>, enabling transforms like Columns or Gallery straight into a Grid variation.<\/p>\n\n\n\n<h3 id=\"more-theme-facing-block-updates\" class=\"wp-block-heading\">More theme-facing block updates<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Smaller changes worth noting: <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/73320\">Global Styles gained <code>textShadow<\/code><\/a> support in Gutenberg 23.5; block visibility metadata is <a href=\"https:\/\/core.trac.wordpress.org\/changeset\/62539\">now honored in excerpts<\/a>, and blocks with <code>visibility: false <\/code>are <a href=\"https:\/\/core.trac.wordpress.org\/changeset\/62586\">hidden everywhere<\/a>; the Verse block supports background gradients; the <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/77017\">Icon block gained flip and rotate controls<\/a> plus <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79111\"><code>block.json<\/code> default icon support<\/a>; a <a href=\"https:\/\/core.trac.wordpress.org\/changeset\/62520\"><code>wp-elements-*<\/code> class collision was fixed<\/a>; and <code>calc()<\/code> expressions now <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/79786\">accept unitless zeros<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Also worth keeping an eye on: an experimental <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/78796\">Dynamic Gallery block variation<\/a> landed in Gutenberg that automatically renders media attached to the post, a first step toward folder- and tag-driven galleries. This is experimental \u2014 test it in Gutenberg, but do not build on it yet.<\/p>\n\n\n\n<h2 id=\"playground\" class=\"wp-block-heading\">Playground<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The Playground team shipped releases v3.1.39 through v3.1.43 during the window. A changelog automation bug left those release notes empty (since <a href=\"https:\/\/github.com\/WordPress\/wordpress-playground\/pull\/3800\">fixed<\/a>), so here is what actually landed.<\/p>\n\n\n\n<h3 id=\"blueprint-steps-you-can-use-today\" class=\"wp-block-heading\">Blueprint steps you can use today<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Blueprint authors picked up several practical upgrades. The <code>installPlugin<\/code> step gained <a href=\"https:\/\/github.com\/WordPress\/wordpress-playground\/pull\/3852\"><code>activationOptions<\/code><\/a>, making setup data available during the activation hook, plus <a href=\"https:\/\/github.com\/WordPress\/wordpress-playground\/pull\/3853\"><code>onError: \"skip-plugin\"<\/code><\/a> for optional installs that should not fail the whole Blueprint (themes got the <a href=\"https:\/\/github.com\/WordPress\/wordpress-playground\/pull\/3854\">same treatment<\/a>). WXR imports gained controls to <a href=\"https:\/\/github.com\/WordPress\/wordpress-playground\/pull\/3877\">preserve source URLs<\/a>, <a href=\"https:\/\/github.com\/WordPress\/wordpress-playground\/pull\/3878\">skip attachments<\/a>, <a href=\"https:\/\/github.com\/WordPress\/wordpress-playground\/pull\/3880\">skip comments<\/a>, and <a href=\"https:\/\/github.com\/WordPress\/wordpress-playground\/pull\/3887\">set a default author<\/a>. And rewrite rules are now <a href=\"https:\/\/github.com\/WordPress\/wordpress-playground\/pull\/3851\">flushed automatically<\/a> after setting permalinks via <code>setSiteOptions<\/code>.<\/p>\n\n\n\n<h3 id=\"mcp-meets-the-abilities-api\" class=\"wp-block-heading\">MCP meets the Abilities API<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Personal Playground <a href=\"https:\/\/github.com\/WordPress\/wordpress-playground\/pull\/3804\">gained MCP support<\/a> along with a <code>playground_ability<\/code> meta-tool: instead of exposing one MCP tool per registered ability, agents can list, inspect, and execute abilities through a single tool. It is a nice illustration of the Abilities API working as designed \u2014 the same abilities proposed for Core merge above become directly callable by AI agents in Playground.<\/p>\n\n\n\n<h3 id=\"personal-playground-remote-access-over-webrtc\" class=\"wp-block-heading\">Personal Playground: remote access over WebRTC<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">You can now <a href=\"https:\/\/github.com\/WordPress\/wordpress-playground\/pull\/3758\">open your Personal Playground from another device over WebRTC<\/a>. The relay server only handles signaling; the actual traffic flows browser to browser.<\/p>\n\n\n\n<h3 id=\"blueprint-v2-is-coming-together\" class=\"wp-block-heading\">Blueprint v2 is coming together<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Roughly 30 merged PRs built out the Blueprint v2 compiler, including <a href=\"https:\/\/github.com\/WordPress\/wordpress-playground\/pull\/3902\">a <code>compileBlueprintForExecution()<\/code> facad<\/a>e and <a href=\"https:\/\/github.com\/WordPress\/wordpress-playground\/pull\/3890\">PHP\/WordPress version-constraint resolution<\/a>. This is infrastructure in progress, not an announced feature \u2014 the v2 syntax is not ready to use yet, but the pace suggests it is worth following.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">CLI users also got fixes for a <a href=\"https:\/\/github.com\/WordPress\/wordpress-playground\/pull\/3833\">SQLite crash on shutdown<\/a> and <a href=\"https:\/\/github.com\/WordPress\/wordpress-playground\/pull\/3811\">mount preservation for long-running sessions<\/a>, and Playground&#8217;s SQLite journal mode now <a href=\"https:\/\/github.com\/WordPress\/wordpress-playground\/pull\/3909\">defaults to DELETE<\/a>.<\/p>\n\n\n\n<h3 id=\"user-facing-changes\" class=\"wp-block-heading\">User-facing changes<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A few smaller updates land closer to the user side but are worth knowing about: the Site Editor now <a href=\"https:\/\/make.wordpress.org\/core\/2026\/07\/01\/whats-new-in-gutenberg-23-5-july-1-2026\/\">respects admin color schemes<\/a>, real-time collaboration <a href=\"https:\/\/github.com\/WordPress\/gutenberg\/pull\/78984\">can be disabled per post type<\/a>, and new-user notification emails <a href=\"https:\/\/core.trac.wordpress.org\/changeset\/62590\">no longer include the username<\/a>. On the security side, oEmbed provider URLs are now <a href=\"https:\/\/core.trac.wordpress.org\/changeset\/62501\">validated before use<\/a>.<\/p>\n\n\n\n<h2 id=\"resources\" class=\"wp-block-heading\">Resources<\/h2>\n\n\n\n<h3 id=\"developer-blog\" class=\"wp-block-heading\">Developer Blog<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">One new tutorial was published on the Developer Blog in the past month:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#8211; <a href=\"https:\/\/developer.wordpress.org\/news\/2026\/06\/dynamically-loading-template-parts-in-block-themes\/\">Dynamically loading template parts in block themes<\/a><\/p>\n\n\n\n<h3 id=\"general\" class=\"wp-block-heading\">General<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">&#8211; <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/17\/whats-new-in-gutenberg-23-3-03-jun-2\/\">What&#8217;s new in Gutenberg 23.4 (June 17)<\/a> and <a href=\"https:\/\/make.wordpress.org\/core\/2026\/07\/01\/whats-new-in-gutenberg-23-5-july-1-2026\/\">What&#8217;s new in Gutenberg 23.5 (July 1)<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#8211; <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/22\/wordpress-7-0-release-retrospective\/\">WordPress 7.0 release retrospective<\/a> \u2014 the survey is open until July 20<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#8211; <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/18\/wordpress-7-0-1-release-schedule\/\">WordPress 7.0.1 release schedule<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#8211; <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/30\/guidelines-for-syncing-code-from-gutenberg-into-wordpress-develop\/\">Guidelines for syncing code from Gutenberg into wordpress-develop<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#8211; <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/17\/recap-restoring-removed-version-history\/\">Recap: restoring removed version history<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#8211; <a href=\"https:\/\/make.wordpress.org\/core\/2026\/06\/15\/core-committers-meeting-wordcamp-europe-2026\/\">Core Committers meeting at WordCamp Europe 2026<\/a><\/p>\n\n\n\n<p class=\"has-text-align-right wp-block-paragraph\"><em>Props to <a href='https:\/\/profiles.wordpress.org\/bph\/' class='mention'><span class='mentions-prefix'>@<\/span>bph<\/a> and <a href='https:\/\/profiles.wordpress.org\/greenshady\/' class='mention'><span class='mentions-prefix'>@<\/span>greenshady<\/a> for reviewing this article.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>July is the month the WordPress 7.1 cycle gets real. Beta 1 lands on July 15, betas follow weekly through the end of the month, and the final release is scheduled for August 19, 2026, timed with WordCamp US. If June was about wrapping up WordPress 7.0, July is about deciding what you need to test before 7.1 locks in.<\/p>\n","protected":false},"author":7543064,"featured_media":6245,"comment_status":"open","ping_status":"closed","sticky":true,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"edge","default_image_id":0,"font":"","enabled":false},"version":2},"_wpas_customize_per_network":false,"jetpack_post_was_ever_published":false},"categories":[53,158,40,38,39],"tags":[65],"class_list":["post-6232","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blocks","category-playground","category-plugins","category-themes","category-updates","tag-roundup","mentions-bph","mentions-greenshady"],"revision_note":"","jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/developer.wordpress.org\/news\/files\/2026\/07\/whats-new-devs-july.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/developer.wordpress.org\/news\/wp-json\/wp\/v2\/posts\/6232","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/developer.wordpress.org\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/developer.wordpress.org\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/developer.wordpress.org\/news\/wp-json\/wp\/v2\/users\/7543064"}],"replies":[{"embeddable":true,"href":"https:\/\/developer.wordpress.org\/news\/wp-json\/wp\/v2\/comments?post=6232"}],"version-history":[{"count":12,"href":"https:\/\/developer.wordpress.org\/news\/wp-json\/wp\/v2\/posts\/6232\/revisions"}],"predecessor-version":[{"id":6248,"href":"https:\/\/developer.wordpress.org\/news\/wp-json\/wp\/v2\/posts\/6232\/revisions\/6248"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/developer.wordpress.org\/news\/wp-json\/wp\/v2\/media\/6245"}],"wp:attachment":[{"href":"https:\/\/developer.wordpress.org\/news\/wp-json\/wp\/v2\/media?parent=6232"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/developer.wordpress.org\/news\/wp-json\/wp\/v2\/categories?post=6232"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/developer.wordpress.org\/news\/wp-json\/wp\/v2\/tags?post=6232"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}