Title: What’s new for developers? (August 2026) Author: Justin Tadlock Published: August 10, 2026 Last modified: September 10, 2026 --- * [Showcase](https://wordpress.org/showcase/) * [Plugins](https://wordpress.org/plugins/) * [Themes](https://wordpress.org/themes/) * [Hosting](https://wordpress.org/hosting/) * [News](https://wordpress.org/news/) - [Learn WordPress](https://learn.wordpress.org/) - [Documentation](https://wordpress.org/documentation/) - [Education](https://wordpress.org/education/) - [Forums](https://wordpress.org/support/forums/) - [Developers](https://developer.wordpress.org/) - [Blocks](https://wordpress.org/blocks/) - [Patterns](https://wordpress.org/patterns/) - [Photos](https://wordpress.org/photos/) - [Openverse ︎](https://openverse.org/) - [WordPress.tv ︎](https://wordpress.tv/) * - [About WordPress](https://wordpress.org/about/) - [Make WordPress](https://make.wordpress.org/) - [Events](https://events.wordpress.org/) - [Five for the Future](https://wordpress.org/five-for-the-future/) - [Enterprise](https://wordpress.org/enterprise/) - [Gutenberg ︎](https://wordpress.org/gutenberg/) - [Job Board ︎](https://jobs.wordpress.net/) * [Swag ︎](https://mercantile.wordpress.org/) * [Get WordPress](https://wordpress.org/download/) Search in WordPress.org [ Get WordPress ](https://wordpress.org/download/) [WordPress Developer Blog](https://developer.wordpress.org/news) What’s new for developers? (August 2026) * [Snippets](https://developer.wordpress.org/news/snippets/) - [Blocks](https://developer.wordpress.org/news/category/blocks/) - [Concepts](https://developer.wordpress.org/news/category/concepts/) - [Common APIs](https://developer.wordpress.org/news/category/common-apis/) - [Design](https://developer.wordpress.org/news/category/design/) - [Playground](https://developer.wordpress.org/news/category/playground/) - [Plugins](https://developer.wordpress.org/news/category/plugins/) - [Themes](https://developer.wordpress.org/news/category/themes/) * - [About this site](https://developer.wordpress.org/news/about/) - [Updates](https://developer.wordpress.org/news/category/updates/) - [How to contribute](https://developer.wordpress.org/news/how-to-contribute/) - [Tips and guidelines](https://developer.wordpress.org/news/tips-and-guidelines-for-writers/) * [Subscribe](https://developer.wordpress.org/news/subscribe/) * [Developer Resources](https://developer.wordpress.org/) * [Snippets](https://developer.wordpress.org/news/snippets/) - [Blocks](https://developer.wordpress.org/news/category/blocks/) - [Concepts](https://developer.wordpress.org/news/category/concepts/) - [Common APIs](https://developer.wordpress.org/news/category/common-apis/) - [Design](https://developer.wordpress.org/news/category/design/) - [Playground](https://developer.wordpress.org/news/category/playground/) - [Plugins](https://developer.wordpress.org/news/category/plugins/) - [Themes](https://developer.wordpress.org/news/category/themes/) * - [About this site](https://developer.wordpress.org/news/about/) - [Updates](https://developer.wordpress.org/news/category/updates/) - [How to contribute](https://developer.wordpress.org/news/how-to-contribute/) - [Tips and guidelines](https://developer.wordpress.org/news/tips-and-guidelines-for-writers/) * [Subscribe](https://developer.wordpress.org/news/subscribe/) * [Developer Resources](https://developer.wordpress.org/) # What’s new for developers? (August 2026) By [Justin Tadlock](https://profiles.wordpress.org/greenshady/) August 10, 2026 [Blocks](https://developer.wordpress.org/news/category/blocks/), [Playground](https://developer.wordpress.org/news/category/playground/), [Plugins](https://developer.wordpress.org/news/category/plugins/), [Themes](https://developer.wordpress.org/news/category/themes/) August is a big month for WordPress. Version 7.1 is scheduled to land on August 19, and it’s arriving on the last day of [WordCamp US](https://us.wordcamp.org/2026/) in Phoenix, which runs August 16–19. Release day during the flagship event of the year is a nice bit of scheduling, and if you’re going to be there, you’ll get to watch it happen live. Both RC1 and RC2 have shipped in the last week. That means the feature set is locked and the [Field Guide](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/) is out. Two security releases also landed in the past month. [WordPress 7.0.2](https://wordpress.org/news/2026/07/wordpress-7-0-2-release/) arrived on July 17 to address one critical and one high severity issue. The severity was high enough that WordPress.org enabled forced updates for affected versions. Then [WordPress 7.0.3](https://wordpress.org/news/2026/08/wordpress-7-0-3-release/) shipped on August 6 with a dozen more fixes. If any site you maintain somehow missed both auto-updates, go handle that before you read the rest of this post. With nine days left before 7.1 ships, this is your last comfortable window to test your plugins and themes against it. Let’s get into what’s new. As always, you can test the latest by running WordPress trunk along with the newest Gutenberg release, or by spinning up a [Playground instance](https://playground.wordpress.net/?php=8.0&wp=beta&networking=no&language=&multisite=no&random=y4q1rn88xn) with no setup at all. Table of Contents 1. [Highlights](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#highlights) 2. a. [The 7.1 Field Guide is out](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#the-7-1-field-guide-is-out) b. [Responsive block styles land in Core](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#responsive-block-styles-land-in-core) c. [Pseudo and custom style states](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#pseudo-and-custom-style-states) d. [The SVG Icon API now public](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#the-svg-icon-api-now-public) e. [The post editor is always iframed](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#the-post-editor-is-always-iframed) 3. [Plugins and tools](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#plugins-and-tools) 4. a. [List table row headers have moved](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#list-table-row-headers-have-moved) b. [The Abilities API updates](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#the-abilities-api-updates) c. [Design System theming for admin interfaces](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#design-system-theming-for-admin-interfaces) d. [Components drop the 40px opt-in for good](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#components-drop-the-40px-opt-in-for-good) e. [Accessible tooltips arrive in the admin](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#accessible-tooltips-arrive-in-the-admin) f. [Block API and editor extensibility](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#block-api-and-editor-extensibility) g. [Filtering Site Editor screens](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#filtering-site-editor-screens) h. [Widget primitives](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#widget-primitives) i. [Notes and collaboration](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#notes-and-collaboration) j. [Other Core changes worth a look](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#other-core-changes-worth-a-look) k. [React 19 is punted again](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#react-19-is-punted-again) l. [WordPress Coding Standards](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#wordpress-coding-standards) 5. [Themes](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#themes) 6. a. [Three new design tools](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#three-new-design-tools) b. [The Navigation block stops propagating font size](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#the-navigation-block-stops-propagating-font-size) c. [Global Styles values show up in the inspector](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#global-styles-values-show-up-in-the-inspector) d. [Playlist and Tabs are stable](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#playlist-and-tabs-are-stable) e. [Other theme-facing changes](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#other-theme-facing-changes) 7. [Playground](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#playground) 8. a. [A new interface, and a handbook to go with it](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#a-new-interface-and-a-handbook-to-go-with-it) b. [Programmatic site management](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#programmatic-site-management) 9. [Resources](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#resources) 10. a. [Developer Blog](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#developer-blog) b. [Developer notes](https://developer.wordpress.org/news/2026/08/whats-new-for-developers-august-2026/#developer-notes) ## Highlights ### The 7.1 Field Guide is out The [WordPress 7.1 Field Guide](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/) is published, and it is the single most important thing to read this month. It collects every release dev note in one place: Media, Accessibility, the Abilities API, Global Styles, the SVG Icon API, DataViews and View Config, the Editor, the Design System, the persistent admin bar, and external libraries. The section on [what didn’t make the release](https://make.wordpress.org/core/2026/08/05/wordpress-7-1-field-guide/#what-changes-didn-t-make-the-7-1-release) is equally useful. Real-time collaboration is not enabled in 7.1. The plan to hide the Classic block from the inserter was reverted. React 19 has been punted again. The **On This Day** dashboard widget didn’t land, and the Guidelines/Knowledge merge proposal continues to evolve. If you’ve been tracking any of those in these previous roundups, that’s where they stand. ### Responsive block styles land in Core ![WordPress post editor with the "preview" dropdown selected. The Tablet view is selected and the Responsive Styles item is selected to edit styles in tablet mode.]( https://developer.wordpress.org/news/files/2026/08/responsive-styles.webp) Responsive style states have been a work in progress in these roundups since spring. [In WordPress 7.1, they ship.](https://make.wordpress.org/core/2026/08/05/responsive-block-styles-and-configurable-viewports-in-wordpress-7-1/) Styles can now be defined for tablet and mobile viewports, both in Global Styles per block type and on individual block instances. In `theme.json`, they’re nested under `@mobile` and `@tablet` keys: ```language-json "styles": { "blocks": { "core/group": { "spacing": { "padding": { "top": "3rem" } }, "@mobile": { "spacing": { "padding": { "top": "1rem" } } } } } } ``` There is no `@desktop` key, and that’s on purpose. The block’s default style is the desktop style, and it continues to apply at every viewport for any property you don’t override. **The part you might’ve been waiting for:** themes can now [configure the breakpoints themselves](https://core.trac.wordpress.org/ticket/65596) via a new top-level `settings.viewport` property in `theme.json`. The defaults are` 480px` for mobile and `782px` for tablet. The values must be non-negative lengths in `px`, `em`, or `rem`. CSS functions, percentages, and unitless values are ignored. And if the tablet value is equal to or lower than the mobile value, only mobile is used. It’s a top-level setting, so you can’t configure it per block type. Blocks that use standard block supports get responsive styles for free. That covers typography, color, background, border, dimensions, spacing, and layout. Blocks with custom style controls do not. That’s the line to check your own blocks against. You can also [turn off responsive editing](https://github.com/WordPress/gutenberg/pull/80814) for users with a quick filter: ```php add_filter( 'block_editor_settings_all', 'example_disable_responsive_editing' ); function example_disable_responsive_editing( $settings ) { $settings['responsiveEditingEnabled'] = false; return $settings; } ``` Note that responsive styles support means changing block-level CSS in Core. [Preset utility selectors](https://make.wordpress.org/core/2026/08/04/miscellaneous-block-editor-changes-in-wordpress-7-1/#block-level-preset-classes-now-match-root-level-specificity) are now wrapped in `:where()`. ### Pseudo and custom style states ![WordPress Site Editor with the Styles > Blocks > Button panel open. The "Hover" state for the button is selected for customization.](https://developer.wordpress. org/news/files/2026/08/pseudo-states.webp) Alongside responsive styles, another oft-requested theme dev feature has landed: [support for pseudo-state styling](https://make.wordpress.org/core/2026/08/05/pseudo-and-custom-style-states-in-wordpress-7-1/). You can define `:hover`, `:focus`, `:focus-visible`, and `:active` in `theme.json` and via the editor. For now, this is limited to the Button and Navigation Link blocks. Here’s an example of styling `:hover` for a Button block (with responsive styling!): ```language-json "core/button": { ":hover": { "color": { "background": "var:preset|color|contrast" } }, "@mobile": { ":hover": { "color": { "background": "var:preset|color|contrast-2" } } } } ``` There’s also an early custom states feature, currently `theme.json`-only with no user-facing UI, used by the Navigation Link block to style the current menu item via a `-current` property. Custom states use a `-` prefix and generate CSS that targets a class name declared through a block’s `block.json` `selectors.states` property. Worth knowing about now, even though it’s narrow today. Like responsive editing, this has its own opt-out: the `blockStatesEditingEnabled` editor setting. ### The SVG Icon API now public ![Modal popup in the WordPress post editor that displays the Icon Library. A custom collection is selected showing various custom SVG icons.](https://developer.wordpress. org/news/files/2026/08/custom-icons.webp) WordPress 7.0 shipped a bundled set of SVG icons for the editor and the Icon block. In 7.1, [it becomes a proper public API](https://make.wordpress.org/core/2026/07/24/registering-and-rendering-svg-icons-in-wordpress-7-1/) that you can register into. Every icon belongs to a collection, and the collection name becomes a namespace prefix, which is what keeps `my-plugin/star` from colliding with `core/star`. Register the collection with `wp_register_icon_collection()`, then add icons with `wp_register_icon()`. And `wp_get_icon()` renders an icon anywhere in PHP with optional size, class, and label arguments. There are two limitations to plan around: * Registered SVGs are sanitized through `wp_kses` against a deliberately conservative allowlist: only ``, ``, and ``. [Work to broaden the allowlist is underway](https://github.com/WordPress/gutenberg/pull/75550). * `fill` is only allowed on the shapes, not the outer ``, and `wp_get_icon()` doesn’t add one. Inside the Icon block this doesn’t matter, because the block stylesheet sets it to the current color. But a standalone `wp_get_icon()` call renders in the SVG’s own fill (black), not the surrounding text color. Recommended: supply your own CSS against the class you pass in. ### The post editor is always iframed This one has been coming since the template editor moved into an iframe in WordPress 5.8. In 7.1, [the post editor takes the final step](https://make.wordpress.org/core/2026/08/03/iframed-editor-changes-in-wordpress-7-1/): it is always iframed, regardless of theme type, the block API versions of registered blocks, or the block API versions of blocks in the content. Sites that register legacy meta boxes are included. In 7.0, the decision was made per post based on what blocks were inserted, which meant the editor could switch between iframed and non-iframed modes depending on content. That conditional behavior is gone. Most blocks already work without changes. The issues that do surface almost always trace back to one root cause: the iframe has its own document and window, separate from the admin page where editor scripts run. Code reaching for the global document or window to touch the canvas is looking at the wrong document. The usual fixes are getting the canvas document from an element inside it via `ownerDocument` and` defaultView`, and using `useRefEffect` to attach and clean up listeners on canvas elements. The handbook’s [technical considerations for the iframe editor](https://developer.wordpress.org/block-editor/reference-guides/block-api/block-api-versions/block-migration-for-iframe-editor-compatibility/#technical-considerations-for-the-iframe-editor) covers the full list. ## Plugins and tools ### List table row headers have moved This is the change most likely to quietly break something you maintain. In [changeset 62838](https://core.trac.wordpress.org/changeset/62838), the primary `th scope="row"` in post list tables [moved from the checkbox column to the title column](https://make.wordpress.org/core/2026/08/03/post-list-tables-row-headers-changed/). The checkbox cell is now a `td`, the title cell is now a `th` carrying an `aria- label` with the post title, and collapsed cells in the responsive view use flex layout. It’s a real accessibility win: screen readers now identify each row by the post rather than by a checkbox that may not even be present. But this is markup that has been largely stable since 2010, and plenty of extensions depend on it implicitly. Check any CSS or JavaScript selecting `th.check-column`, or expecting row actions and post titles inside a `td`. ### The Abilities API updates The Abilities API shipped as infrastructure in WordPress 6.9. In 7.1 it picks up nearly everything you’d need to actually build against it: a filterable execution lifecycle, custom validation, and a shared discovery pipeline. If you’re building AI integrations, automation tooling, or protocol adapters, this is the release where the API stops being a foundation and starts being a toolkit. Five dev notes cover it, and they’re worth reading in this order: * [New execution lifecycle filters](https://make.wordpress.org/core/2026/07/29/new-execution-lifecycle-filters-for-the-abilities-api-in-wordpress-7-1/) * [Abilities API improvements](https://make.wordpress.org/core/2026/07/31/abilities-api-improvements-in-wordpress-7-1/) * [Filtering registered abilities with wp_get_abilities()](https://make.wordpress.org/core/2026/08/05/filtering-registered-abilities-with-wp_get_abilities-in-wordpress-7-1/) * [A unified public exposure flag](https://make.wordpress.org/core/2026/08/04/a-unified-public-exposure-flag-for-abilities-in-wordpress-7-1/) * [JSON Schema preparation for client compatibility](https://make.wordpress.org/core/2026/07/31/json-schema-preparation-for-client-compatibility-in-wordpress-7-1/) ### Design System theming for admin interfaces WordPress 7.1 ships [foundational support for theming admin interface components](https://make.wordpress.org/core/2026/07/31/design-system-theming-in-wordpress-7-1/), covering color, roundness, and cursor styles. Note that this has nothing to do with the front end. “Theming” in this instance is directly related to the admin. The `wp-theme` stylesheet provides a full set of semantic design tokens as CSS custom properties, so you can reference them instead of hardcoding values. The `wp-theme` script handle provides a `ThemeProvider` React component that wraps a section of a page and overrides those token values. Give it a pair of seed colors and it generates a harmonious ramp for you.  For plugin authors who’ve wanted their admin screens to carry their own brand while still looking like they belong in WordPress, this is the first real opening. The [token reference](https://github.com/WordPress/gutenberg/blob/wp/7.1/packages/theme/docs/tokens.md) lists what’s available. ### Components drop the 40px opt-in for good The `__next40pxDefaultSize` prop has finished its journey. It was introduced in 6.7, soft-deprecated in 6.8, and as of 7.1 it’s [a no-op](https://make.wordpress.org/core/2026/07/23/editor-components-updates-in-wordpress-7-1/). Form controls render at 40px unconditionally, and passing `__next40pxDefaultSize ={false}` no longer opts back out to 36px. Remove the prop from your usage; there’s no replacement. If you were passing `size="__unstable-large"` only to get the taller control, remove that too. On `BorderBoxControl`, `BorderControl`, `FontSizePicker`, and `ToggleGroupControl`, the `size` prop is deprecated as well. ### Accessible tooltips arrive in the admin Tooltips have existed in the editor for a while, but not in the rest of wp-admin. WordPress 7.1 adds `wp_get_tooltip()` and `wp_get_toggletip()` [to close that gap](https://make.wordpress.org/core/2026/08/03/introducing-name-and-informational-tool-tips-in-wordpress-7-1/). The first gives a visible accessible name to icon-only controls; the second adds a triggerable button for extended help text. Core uses them on post meta box controls and the login screen’s “Remember Me” checkbox respectively. The CSS loads globally, but the JavaScript only loads where Core uses it. Elsewhere, enqueue `wp-tooltip` for both. ### Block API and editor extensibility Several miscellaneous items are worth looking at that could affect your code: * Block transforms can now [target a specific variation](https://github.com/WordPress/gutenberg/pull/78713) via `variationName`, and `switchToBlockType()` accepts a variation as a third argument. * `__experimentalCloneSanitizedBlock` and `__experimentalSanitizeBlockAttributes` are [stabilized](https://github.com/WordPress/gutenberg/pull/79928). The experimental names still work but now log deprecations. * Non-paginated entities [now return all records](https://github.com/WordPress/gutenberg/pull/76406). If you were getting a truncated list of ten back from `getEntityRecords()`, you’ll now get everything, so check anywhere you render without your own limit. * Template parts can [opt out of content-only editing](https://github.com/WordPress/gutenberg/pull/79191) with the new `disableContentOnlyForTemplateParts` setting. Elsewhere in Gutenberg 23.6 and 23.7: block bindings [share context assembly between call sites](https://github.com/WordPress/gutenberg/pull/79855), PHP-only blocks [forward the current post ID to server render](https://github.com/WordPress/gutenberg/pull/78909), the inspector controls styles slot [moved back to its previous position](https://github.com/WordPress/gutenberg/pull/80111), and `PluginPostStatusInfo` is [now available in the DataForm post summary](https://github.com/WordPress/gutenberg/pull/79586). The Interactivity API also [refactored its directives into self-registering modules](https://github.com/WordPress/gutenberg/pull/79975). ### Filtering Site Editor screens Four new filters let you configure the `DataViews` and `DataForm` components powering the Pages, Templates, Parts, and Patterns screens:  * `get_entity_view_config_posttype_page` * `get_entity_view_config_posttype_wp_template` * `get_entity_view_config_posttype_wp_template_part` * `get_entity_view_config_posttype_wp_block` Each can set default_view, default_layouts, view_list, and form, so you can control default layout and sort order, which layouts users can pick, the preconfigured views in the sidebar, and the Quick Edit form. Callbacks receive a config object with methods for merging patches, and they must return the container. The [dev note](https://make.wordpress.org/core/2026/07/31/filtering-site-editor-screens-in-wordpress-7-1/) has a working example, and the mechanism is designed to grow to other entities. On the Gutenberg side, view config also [gained version handling](https://github.com/WordPress/gutenberg/pull/79809) and [stricter merge semantics](https://github.com/WordPress/gutenberg/pull/80571). ### Widget primitives Work on the widget dashboard continued through both Gutenberg releases, mostly in the direction of typed, declarative widget definitions: * Widget primitives now [ship as a script module](https://github.com/WordPress/gutenberg/pull/80149). * New [`WidgetAttributeField`](https://github.com/WordPress/gutenberg/pull/79544) for typed attribute schemas, backed by a [field type registry](https://github.com/WordPress/gutenberg/pull/80148). * The widget category is [exposed through the build pipeline and REST API](https://github.com/WordPress/gutenberg/pull/79638). * New declarative [help metadata field](https://github.com/WordPress/gutenberg/pull/79830) and [relevance attribute](https://github.com/WordPress/gutenberg/pull/79735). * `title`, `description`, and `keywords` are [translated server-side](https://github.com/WordPress/gutenberg/pull/79701). Dashboard widgets also picked up [action href sanitization](https://github.com/WordPress/gutenberg/pull/80510) and [help link sanitization](https://github.com/WordPress/gutenberg/pull/80409). ### Notes and collaboration Real-time collaboration isn’t in 7.1, but Notes picked up two features since Beta 1: [email notifications for @mentions](https://github.com/WordPress/gutenberg/pull/79606) and [shareable revision links](https://github.com/WordPress/gutenberg/pull/79934). Notes are also [now excluded from comment feed queries](https://core.trac.wordpress.org/ticket/65613), which relates to a disclosure issue patched in 7.0.3. ### Other Core changes worth a look * The `notify_post_author` [filter now has the final say](https://make.wordpress.org/core/2026/08/05/the-notify_post_author-filter-now-has-the-final-say-on-post-author-notifications/). Approval status is folded into the default, so a `__return_true` callback will now also send mail for comments in moderation, spam, or trash. * The toolbar [now persists across editor screens](https://make.wordpress.org/core/2026/07/13/consistent-navigation-in-wordpress-7-1-with-persistent-toolbar/). If you extend it, test how your items behave during client-side navigation. * [Speculative loading can be configured](https://core.trac.wordpress.org/ticket/65624) via environment variables and constants. * `_doing_it_wrong()` messages in `WP_Block_Type_Registry::register()` [gained context](https://core.trac.wordpress.org/ticket/65039). * `get_file_data()` [now recognizes headers prefixed](https://core.trac.wordpress.org/ticket/42517) by a `