Aditya Dhade 5:09 pm on July 14, 2026
Tags: , , , ,   

Performance Chat Summary: 14 July 2026

The full chat log is available beginning here on Slack.

WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets

  • @westonruter shared a late submission for inclusion in WordPress 7.1 and requested reviews for PR #12514, which provides a mechanism for hosting providers to change the default Speculative Loading eagerness and mode without requiring an mu-pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party..
    • @swissspidy shared that CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. was a bit hesitant in the past to introduce new constants, let alone environment variables, and asked whether this is something hosts could control with an mu-plugin instead.
    • @westonruter replied that there is such an environment variable and constant for wp_get_environment_type().
    • @westonruter shared that configuration of Realtime Collaboration was also being done via environment variables.
    • @westonruter shared that the reason for the environment variable is explained in the Realtime Collaboration discussion, where a host may not be able to control all the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher being used in a hosted site and hosts could potentially control the PHP being used but may not “manage” their hosted WordPress sites, so doing so would be a violation of sorts of what their customers expect.

Performance Lab Plugin (and other performance plugins)

  • @westonruter shared that there are some new PRs that need reviewing, but has not had time to review them yet due to work on Core tickets and expressed hope that there would be more time available for reviews within the next week.

Our next chat will be held on Tuesday, July 28, 2026 at 16:00 UTC in the #core-performance channel in Slack.

#core-performance, #hosting, #performance, #performance-chat, #summary

Amy Kamala 5:08 am on July 14, 2026
Tags: , , ,   

Dev Chat Agenda – July 14, 2026

The next WordPress Developers Chat will take place on Tuesday, July 14, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

The various curated agenda sections below refer to additional items. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.

Announcements 📢

Note: Dev Chat has been moved to Tuesdays at 15:00 UTC for the duration of the 7.1 release cycle.

7.1

  • 7.1 BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is due for release this Wednesday, July 15th. The release party starts at 15:00 UTC.
  • New Dev Notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.: Consistent navigation in WordPress 7.1 with persistent toolbar

General

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

Open floor  🎙️

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

#7-1, #agenda, #core, #dev-chat
Jonathan Desrosiers 6:02 pm on July 8, 2026  

Transitioning To Rulesets In The Gutenberg Repository

As of ~16:00UTC today (8 July 2026), all rules configured to enforce the desired contributor workflows and quality requirements in the GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ repository have been converted from branch protection rules to repository rulesets. This was done to fix a broken step in the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. release process where the GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ app responsible for pushing version bump commits to trunk was unable to do so.

While rulesets are an iteration on branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". protection rules, they are not a flat out replacement and can be used together. However, they do have several advantages over branch protection rules, including more flexibility, the ability to layer them, and being publicly accessible for contributors to understand why they may be unable to perform a certain action on a specific branch.

After looking through the pre-existing protection rules, there did not appear to be any benefit to keeping any one branch protection rule over a ruleset. Best efforts were made to ensure the new rulesets function identically to the previous protection rules, but there may be some nuance that was missed.

If you happen to notice any permission or capabilitycapability A capability is permission to perform one or more types of task. Checking if a user has a capability is performed by the current_user_can function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability).-related problems, please mention them in the comments below or share them in #core-editor so they can be fixed.

Props @jorbin for comparing the new rulesets with the previous branch protection rules, and proofreading this post.

Amy Kamala 2:16 am on July 8, 2026
Tags: , , ,   

Dev Chat Agenda – July 8, 2026

The next WordPress Developers Chat will take place on Wednesday, July 8, 2026, at 15:00 UTC in the core channel on Make WordPress Slack.

The live meeting will focus on the discussion for upcoming releases, and have an open floor section.

The various curated agenda sections below refer to additional items. If you have ticketticket Created for both bug reports and feature development on the bug tracker. requests for help, please continue to post details in the comments section at the end of this agenda or bring them up during the dev chat.

Announcements 📢

7.1

  • 7.1 bug scrub schedule
  • BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 is scheduled for next week on Wednesday July 15th at 15:00 UTC
  • Heads up CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Committers: Tech and Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. leads have started tagging tickets for dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.. Deadline for publishing is August 3rd, and the Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. targeted for the 4th (just before RC1).
  • Merge Proposal: Expanding WP Core Abilities
  • Classic block will NOT be hidden from inserter in WP 7.1

General

Discussions 💬

The discussion section of the agenda is for discussing important topics affecting the upcoming release or larger initiatives that impact the Core Team. To nominate a topic for discussion, please leave a comment on this agenda with a summary of the topic, any relevant links that will help people get context for the discussion, and what kind of feedback you are looking for from others participating in the discussion.

  • Dev Chat scheduling during 7.1 cycle

Open floor  🎙️

Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.

Please include details of tickets / PRs and the links in the comments, and indicate whether you intend to be available during the meeting for discussion or will be async.

#7-1, #agenda, #core, #dev-chat

Adrian Duffell 8:09 am on July 3, 2026
Tags: , , ,   

Bug Scrub Schedule for WordPress 7.1

It’s time to get WordPress 7.1 ready for release, and help is needed to ensure it’s smooth and bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.-free. Whether you’re an experienced contributor or joining in for the first time, everyone is welcome! 🎉

Schedule Overview

Regular bug scrubs are being held twice a week with @sajjad67 and @adrianduffell leading them. As the release date approaches and activity ramps up, the number of scrubs may be increased. These efforts will help ensure everything is on track for a smooth launch. Participation is welcome at any of these sessions, so feel free to join. Bring questions, ideas, and let’s scrub some bugs together!

Weekly Bug Scrub Schedule 🗓️

Alpha Bug Scrubs

6 July 2026 09:00 UTC by @sajjad67
9 July 2026 22:00 UTC by @adrianduffell
13 July 2026 09:00 UTC by @sajjad67

BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. Bug Scrubs

Focus: issues reported from the previous beta.

16 July 2026 22:00 UTC by @adrianduffell
20 July 2026 09:00 UTC by @sajjad67
23 July 2026 22:00 UTC by @adrianduffell
27 July 2026 09:00 UTC by @sajjad67
30 July 2026 22:00 UTC by @adrianduffell
3 August 2026 09:00 UTC by @sajjad67

Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). Bug Scrubs

Focus: issues reported from the previous RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta)..

6 August 2026 22:00 UTC by @adrianduffell
10 August 2026 09:00 UTC by @sajjad67
13 August 2026 22:00 UTC by @adrianduffell
17 August 2026 09:00 UTC by @sajjad67

Where?

All scrubs happen in the #core channel on Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. Just hop in at the scheduled time to get started! If you haven’t joined Slack yet, now’s the perfect time.

Want to Lead a Bug Scrub? 

Reach out in Slack, and assistance will be provided to get everything set up. Everyone is welcome—whether you’re a developer, designer, tester, or work on documentation, you can help! Just hop into the #core channel on Slack during any of the scheduled times. No experience? No problem—feel free to ask for help anytime! It’s a great way to contribute, learn new things, and connect with the community.

Check this schedule often, as it will change to reflect the latest information.

What about recurring component scrubs and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions?

For your reference, here are some of the recurring sessions:

Have a recurring component scrub or triage session?

PingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @adrianduffell or @sajjad67 on Slack to have it added to this page.

Want to lead a bug scrub?

Did you know that anyone can lead a bug scrub at any time? Yes, you can!

How? Ping @adrianduffell or @sajjad67 on Slack with the day and time you’re considering as well as the report or tickets you want to scrub.

Planning one that’s 7.1-focused? Awesome! It can be added to the schedule here. You’ll get well deserved props in Dev Chat, as well as in the #props Slack channel!

Where can you find tickets to scrub?

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. handbook.

Props @annezazu for proofreading and review.

#7-1, #bug-scrub, #core

Jb Audras 9:26 pm on July 1, 2026
Tags: , , , ,   

Dev Chat summary: July 1, 2026

Start of the meeting in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/, facilitated by @audrasjb 🔗 See the agenda post.

Announcements 📢

7.1

  • Roadmap for 7.1
  • Recent proposals:
  • Recent dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase.:

7.0.1

General

Discussion 💬

From @amykamala about handbook updates to AI policies

“I’d like to also propose a new policy: disclosure of use of AI in posts and announcements. It can just be a quick sentence at the bottom of the page saying AI tools were used in the creation of this article or something to that affect.”

@westonruter also proposed to apply such a policy to Slack comments, and @desrosj also has some draft for this topic for posts and comments.

@amykamala shared that a draft is being worked on here or here. The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-ai update draft could use some feedback. It’s based on Jonathan’s comments and the comments in the thread. The post comment guidelines draft doesn’t have changes to review yet but folks are welcome to work on it.

@audrasjb advised to use a new section for this topic in the Core Handbook.

Dev Chat scheduling during 7.1 cycle

With all the coming release parties scheduled on Wednesday, it looks like we need to move the meeting to another time slot.

@amykamala and @audrasjb suggest to switch the devchat time slot to 15:00 on Thursdays, starting the week of 7.1 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1.

@jorbin noted that it will conflict with the monthly Developer Blogblog (versus network, site) Editorial Group meeting, the bi-weekly AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) team meetings and a weekly core-test meeting. Which is not a blockerblocker A bug which is so severe that it blocks a release., but worth taking this into account. He also noted that Tuesdays are more open but this day is not the best for Amy and JB.

@joedolson noted that the Accessibility team moved its meeting for the 7.0 schedule, which was also on Thursdays, and they could do that again.

@amykamala and @audrasjb will come up next week with one or two proposals so a decision can be made.

From @dmsnell about concerns about WPCS discrepancies in GitHub and Trac, and proposed change in the general policy

The concern raised in this thread is especially about the array elements alignment rule.

The attendees agreed that while 90% of the time, alignment is prefered, there are some cases where it makes things worse.

From @joedolson: “It seems to me like the primary point of @dmsnell‘s thread was about misaligned standards between GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ and Core, but he seemed to walk that assertion back in the thread? Is there a real issue here? If the standards aren’t aligned, one of them needs to change”

#7-0, #7-0-1, #7-1, #core, #dev-chat

Bero 6:54 pm on July 1, 2026
Tags: , , ,   

What’s new in Gutenberg 23.5? (July 1, 2026)

“What’s new in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/…” posts (labeled with the #gutenberg-new tag) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Editor.

What’s New In
Gutenberg 23.5?

Gutenberg 23.5 has been released and is available for download!

This release adds cropping controls to the Media editor, brings it to the Cover blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience., and extends responsive style states with aspect-ratio, flex-alignment, and text-shadow controls. Other changes include a minimum WordPress version bump to 6.9, Icon block transforms, and real-time collaboration improvements.

Try Gutenberg 23.5

Table of contents

  1. Media Editor Cropping and Cover Block Support
  2. Unified Device Preview and Resizable Editor
  3. Other notable highlights
  4. Changelog
  5. First-time contributors
  6. Contributors

Media Editor Cropping and Cover Block Support

The experimental Media editor gains several cropping improvements: a magnified crop canvas for fine adjustments (79044), crop handles that snap to source pixels (79139), and fixed keyboard resizing for locked aspect-ratio crops (79207). The Cover block now supports the Media editor modal, bringing inline cropping to cover images. (79258)

Unified Device Preview and Resizable Editor

You can now drag the editor canvas to any width, instead of being limited to the Desktop, Tablet, and Mobile presets. The device preview dropdown and the resize handles work together, so you can jump to a preset viewport or fine-tune to an exact width in between. Blocks set to show only on specific viewports respond as you resize, appearing and disappearing at their breakpoints. The preview dropdown also now holds a toggle for responsive editing, making it the central place to both preview your content across screen sizes and make viewport-specific adjustments. (75121)

Other Notable Highlights

  • Minimum WordPress version. The Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. now requires WordPress 6.9 or later (79196).
  • Global Styles adds text shadows. A new textShadow style adds support for configuring text shadows in Global Styles. (73320)
  • Icon block. Adds flip and rotate controls (77017) and inserts a default icon instead of an empty placeholder (79111).
  • Real-time Collaboration. Can now be disabled per post type (78984), and the code-editor cursor no longer jumps to the end on remote sync (79005).
  • ThemeProvider available as a public export. ThemeProvider is now exported directly from @wordpress/theme. (78664)

Changelog

Enhancements

  • Style Engine: Export public TypeScript types. (79079)
  • WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Primitives: Decouple discovery from a hardcoded endpoint. (79322)
  • Widget Primitives: Make @types/react an optional peer dependency. (79272)

Components

  • Add corner radius presets to ThemeProvider. (78816)
  • Autocomplete: Add Group and GroupLabel primitives. (78901)
  • Base Styles: Add wpds-var Sass helper for design token fallbacks. (78698)
  • BaseControl: add text-wrap: Pretty. (79112)
  • BoxControl: Hard deprecate 40px default size. (79419)
  • Components, DataViews: Adopt –wpds-dimension-size-* tokens. (79093)
  • ESLint, UIUI User interface, Components: Mark Tooltip from wordpress/ui as recommended. (78693)
  • Popover: Add open/close motion and fix close re-anchor. (78885)
  • Theme: Add Figma scopes to element size tokens. (79032)
  • Theme: Add disabled variants for brand and error interactive color tokens. (79124)
  • Theme: Add stroke-surface tokens for the caution tone. (79198)
  • Theme: Apply ThemeProvider styles inline (I2). (78678)
  • Theme: Differentiate –wpds-color-fg-interactive-{brand,error}-active vs resting state tokens. (79151)
  • Theme: Enforce sRGB seed-color input contract for ThemeProvider. (79148)
  • Theme: Provide design-system token defaults without a runtime <ThemeProvider>. (78664)
  • Theme: Skip serializing data-wpds-root-provider=”false” on non-root providers. (79253)
  • Theme: forward ThemeProvider cornerRadius preset to :Root for root providers. (79153)
  • UI Field.Description: add text-wrap: Pretty. (79143)
  • UI: Disable instant overlay popup transitions. (79432)
  • UI: Simplify focus ring styles. (78823)
  • UI: Use isomorphic layout effects for SSR. (79458)
  • Update @ariakit/reactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org to 0.4.29. (79055)
  • [DataViewsPicker]: DataViewsPicker.BulkActionToolbar now renders only the bulk-selection info and action buttons. (79180)
  • theme: Rename bg/fg design token groups to background/foreground. (79098)

Block Library

  • Add support for aspect ratio and related controls in viewport states. (78795)
  • Audio: Apply inert directly instead of wrapping in Disabled. (79423)
  • Classic Block: Port PHPUnit coverage for hiding it from the inserter. (79434)
  • Cover block: Add media editor modal. (79258)
  • File Block: Combine audio/video/image to file transforms. (79242)
  • File Block: Replace on-mount downloadButtonText effect with a default variation. (79236)
  • Icon Block: Add flip and rotate transformation controls. (77017)
  • Icon block: Default to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress./info via block.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. instead of an insert-time effect. (79212)
  • Icon block: Move flip controls to toolbar group. (79192)
  • Icons block: Insert an icon by default. (79111)
  • Math format: Seed LaTeX input from the current selection. (79052)
  • Pullquote: Migrate to text-align block support. (79225)
  • Remove orphaned convertToListItems util. (79400)
  • Search block: Add opt-in support for the semantic element. (78485)
  • Tabs: Simplify layout and prune redundant block supports. (77646)
  • Try: Remove Tab (Tab list item) block. (77439)
  • Video: Apply inert directly instead of wrapping in Disabled. (79371)

Post Editor

  • Block Editor: Allow overriding disableContentOnlyForTemplateParts setting. (79191)
  • Editor: Hide cmd palette shortcut in document bar when adminadmin (and super admin) bar is shown. (79060)
  • Feature: Need to add “Show More” / “Show Less” toggle in Note. (77446)
  • Notes: Simplify ‘Show more/less’ collapse logic. (79261)
  • Rename Toolbar in editor experiment to match iteration issue. (79074)
  • RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. screen with picker-activity layout. (77333)
  • Style states: Use symbols for property keys to avoid clashes. (79210)
  • Integrate Resizable Editor with Device Preview and add Responsive editing. (75121)

Site Editor

  • Add xl border radius token for page shell surfaces. (78913)
  • Change ‘Identity’ nav item position. (79292)
  • Handle aria-current natively in SidebarNavigationItem. (79305)
  • Introduce isHidden prop for SidebarNavigationItem. (79352)
  • Omnipresent toolbar: Show site icon instead of dashicon if set. (79049)
  • Update spelling within the welcome tour. (53028)

Block Editor

  • Add flex vertical alignment tool to block inspector layout panel. (79426)
  • Correct behaviour of flex child fixed width and introduce max width option. (79073)
  • Global Styles: Add textShadow style support. (73320)
  • List View block support: Hide list tab when allowedBlocks is empty, with no children. (78932)
  • Pattern editing: Show root block identity when editing pattern sections. (79417)

Media

  • Media Editor Modal: Add a loading and simple error state. (79101)
  • Media Editor: Magnify the crop to fill the canvas. (79044)
  • Media Fields: Ensure the current post is always included in the initial options. (79467)
  • Media editor: Snap crop handles to source pixels. (79139)

Data Layer

  • RTC: Allow disabling collaboration by post type. (78984)
  • TextControl: Hard deprecate 40px default size. (79386)
  • View Config: Request a subset of properties with the _fields parameter. (79355)

Client Side Media

  • Media: Rename HEIC companion metadata key to source_image. (79307)
  • Upload Media: Add error taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies., localized messages, and dev diagnostics. (74917)
  • Vips: Inline WASM with compact UTF-8 binary encoding instead of base64. (79188)

Dashboard

  • Boot: Run page init modules in initSinglePage. (79394)
  • Widget Dashboard: Extract into wordpress/widget-dashboard. (79268)

npm Packages

  • Grid: Prepare wordpress/grid for npm publishing as experimental 0.1.0. (79071)
  • Widget Primitives: Extract into wordpress/widget-primitives. (79134)

DataViews

  • View configuration APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. and REST Endpoint: Make them core ready. (79347)

Plugin

  • Bump minimum required WordPress version to 6.9. (79196)

Global Styles

  • Global styles revisions: Replace active text with badge. (79137)

Icons

  • Add media control and backup icons. (78987)

Block bindings

  • Block bindings : Add support to list-item. (78947)

Bug Fixes

  • Block Bindings: Preserve nested lists when binding List Item content. (79346)
  • Elements tests: Accept both md5 and sequential wp-elements-* class names. (79300)
  • Plugins API: Fix the plugin ‘render’ property validation. (79315)
  • V2 Site Editor: Fix template edit routes. (79230)
  • wp-build: Return null from getPackageInfo on resolve miss instead of throwing. (78715)

Post Editor

  • Block Fields: Fix crash resolving pattern overrides bindings. (79092)
  • DataFormPostSummary: Fix different useSelect returned values. (79478)
  • Editor: Disable saving while a non-post entity is being saved. (79069)
  • Editor: Guard PostViewLink against post types without a labels object. (79160)
  • Mark all controlled/mode block changes non-persistent. (79350)
  • Paste: move spaces out of inline formatting elements. (79637)
  • RTC: Fix code editor cursor jumping to the end on remote sync. (79005)
  • Revisions: Ignore empty []/{} metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. values in the Meta diff panel. (79185)
  • Style Book: Fix crash when previewing variations for blocks without examples. (79131)

Block Library

  • Avoid dirtying related navigation entities during passive render. (79000)
  • Custom HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.: Fix scrollbar becoming non-functional after switching tabs. (78571)
  • Gallery: Hide Navigation button type when lightbox editing is disabled. (79147)
  • Image block: Remove duplicate data-wp-bind–srcset in the lightbox overlay. (79202)
  • Image: Fix pasted images stretching when dimensions are preserved. (79067)
  • Navigation block: Fix responsive style states for typography settings. (79072)

Components

  • BoxControl: Respect a supplied placeholder via inputProps. (79466)
  • DataForm panel layout: Fix double-clicking a field row leaving the flyout stuck open. (79348)
  • DataForm: Fix panel field control overflow clipping and remove button overrides. (79275)
  • Docs: Fix typos in README files. (79331)
  • Fix: Custom HTML block preview keeps expanding when iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. uses height:100vh. (78677)

Block Editor

  • Fix potential crash from ‘useBlockToolbarPopoverProps’. (79178)
  • Fix: State styles – clear background-image when hover sets a solid background-color. (78992)
  • Grid overlays: Use canvas iframe window for viewport visibility detection. (79255)
  • RichText: Fix duplicated format wrappers when typing inside an applied format. (79091)
  • Template Part: Remove restriction on tabs / inspector fills. (79181)

Media

  • Media Editor: Fix crop canvas pinch zoom. (79332)
  • Media Editor: Keep the modal skeleton pinned in the editor flow. (79070)
  • Media editor modal: Fix keyboard resizing for locked aspect-ratio crops. (79207)

Site Editor

  • Fix admin color scheme bleeding through the mobile content scrollbar gutter. (79056)
  • Save hub button styling while saving. (79287)

Command Palette

  • Fix duplicate enqueue breaking the palette in the Site Editor. (79396)

Client Side Media

  • Vips: Bump wasm-vips to 0.0.18 for high-bit-depth AVIF decoding. (79179)

Icons

  • KSES: Allow SVG-specific presentation attributes in safe_style_css. (79172)

Style States

  • Fix responsive element styles front end output. (79135)

Data Layer

  • Core Data: Cleanup edits matching persisted record on undo/redo. (77100)

AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)

Media

  • Media Fields: Avoid focus loss when detaching the current parent. (79468)

Dashboard

  • Revert H1 to “Dashboard” and fix heading hierarchy. (79251)

Components

  • UI Button: Fix loading state in forced colors. (78820)

Performance

  • Blocks: Migrate Markdown converter from showdown to marked. (77953)

Post Editor

  • Use the correct directory for recent preload improvements. (79359)

Experiments

Post Editor

  • Editor Inspector with DataForm – remove revision panel and add link. (79195)
  • al: Expand Editor Inspector: Use DataForm experiment to template parts. (79399)
  • Experimental: Expand Editor Inspector: Use DataForm experiment to templates. (76934)
  • Experimental: Preserve editor panel visibility in the DataForm post summary. (79441)

Site Editor

  • Omnipresent Toolbar: Increase top padding in sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. nav title. (79083)

Block Library

  • Unwrap Classic block migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. notice experiment. (78165)

Documentation

  • Clarify Core-specific steps when bumping support. (79416)
  • ConfirmDialog: Document AlertDialog as successor in Storybook. (79293)
  • Fix Small Typo in block-filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. file. (79367)
  • Panel: Recommend CollapsibleCard for use outside the block inspector. (78863)
  • Storybook: Reorganize design system introduction for first touch-point usefulness. (79360)
  • Storybook: Upgrade Storybook to 10.4. (77382)
  • Theme: Add design tokens maintainer’s guide documentation. (79157)
  • Widget Primitives: Document the experiment-gated REST endpoint. (79264)
  • Widget Primitives: Make contract and story documentation host-agnostic. (79358)
  • design-system-mcp: Improve README overview and setup instructions. (79238)

Code Quality

  • Add lock-unlock route as a workspace and update dependencies. (79138)
  • CI: Disallow new dependencies in the root package.json. (78616)
  • Patterns: Add a missing gap to ‘Enable overrides’ modal. (79421)
  • Refactor npm-package-json-lint configuration and update dependencies. (79223)
  • Refactor to move ‘glob’ dependency to appropriate workspaces. (79145)
  • Refactor to rename ‘wordpress/lock-unlock’ to ‘wordpress/routes-lock-unlock’. (79163)
  • Scripts: Avoid tests getting published to npm. (79204)
  • chore: Remove wordpress/vips dependency from root. (79249)
  • chore: Remove glob from root pkg json. (79183)
  • e2e: Retry transient theme activation failures in pages spec. (79171)
  • fix: Add missing root devDependencies for WordPress packages. (79221)

Components

  • Add Emotion migration guardrails. (79442)
  • Button: Use font weight token. (79278)
  • Complete WPDS token migration for remaining borders. (79003)
  • DataForm: Align label-side gap of panel layout with regular layout. (79311)
  • Make ResizableBox children prop optional. (79370)
  • Migrate Divider to SCSS module. (79444)
  • Migrate compose package to TypeScript. (70618)
  • Popover: Align transition state styles. (79410)
  • Re-land WPDS border token migration with Emotion-safe comments. (79244)
  • Refactor Prettier configuration and update dependencies. (79219)
  • Refactor withFallbackStyles from class to function component. (78837)
  • Refactor: Move stylelint configuration and deps to tools/stylelint workspace. (79226)
  • Restore shared stylelint cursor rule. (79425)
  • Theme: Add tests for ThemeProvider and useThemeProviderStyles. (79126)
  • Theme: Drop –wpds-dimension-base from the public token surface. (79254)
  • Theme: Rename –wpds-color-stroke-focus-brand token to –wpds-color-stroke-focus. (79125)
  • Theme: Run stylelint plugin tests via the Node API. (79199)

Post Editor

  • Edit Post: Refactor MetaBoxesSection to use data hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.. (79433)
  • Edit Post: Refactor and cleanup InitPatternModal component. (79190)
  • Editor: Migrate FlatTermSelector to UI Stack component. (78659)
  • Editor: Refactor AutosaveMonitor to a function component. (79043)
  • Editor: Remove orphaned editor-help component leftovers. (79324)
  • Editor: Use Stack for post summary. (79397)
  • Fields: Move author fields for templates and template parts. (79395)
  • Validation: Add a published-dependency audit script. (79094)

Block Library

  • Blocks: Use positional sprintf placeholders in avatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name., comment, and search renderers. (79290)
  • Image block: Simplify metadata syncing logic by removing chained get entity calls. (79469)
  • Math format: Simplify the onClick handler and use canonical selected-text capture. (79081)
  • Navigation: Use block context to determine whether Page List is nested in Submenu. (79048)
  • Remove unused Babel optimization plugin. (79162)
  • Tabs: Pre-stabilization API cleanup and refactoring. (79337)

Data Layer

  • Core Data: Don’t use ‘useQuerySelect’ in ‘useEntityRecord(s)’ hooks. (76198)
  • Packages: Fix the published dependency surface of npm packages. (79095)

Patterns

  • Add end-to-end coverage for pattern wrapper block identity. (79462)

Media

  • Media Editor: Align crop settle state with transition completion. (79339)

Block Editor

  • Convert utility modules to TypeScript. (79323)

Site Editor

  • Patterns: Migrate modals to wordpress/ui components and fix rename input width. (79233)
  • Theme: Restore public ThemeProvider export. (79620)

Icons

  • Use snake_case file_path key in icon registry. (79100)

Tools

  • Eslint: Move deps from root into tools/eslint and packages/eslint-plugin. (79110)

Testing

  • Automated Testing: Add babel-plugin-transform-import-meta to emulate import.meta.dirname. (79362)
  • Automated Testing: Globally shim Element#getClientRects. (79353)
  • Automated Testing: Use static value for IS_GUTENBERG_PLUGIN env setup. (79201)
  • CI: Run PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher unit tests on PHP 8.4 and 8.5. (79260)
  • Components: Improve Menu unit tests performance by removing sleeps. (79295)
  • E2E: Support WordPress installs served from a subdirectory. (79166)
  • Ignore markdown linting for backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch.-changelog MD files. (79392)
  • devops: Dedicated histories for different node.js versions. (79473)
  • devops: Separate environments for jest date tests. (79453)
  • wp-build: Resolve wordpress/build from __dirname in resolve-miss test. (79208)

Build Tooling

  • Build: Add GUTENBERG_CHECK_INSTALLED_DEPS env var to opt out of installed-deps check. (79068)
  • Build: Replace unmaintained release actions. (78258)
  • Build: Use GUTENBERG_TOKEN when creating the release draft. (79747)
  • Configure Flakiness.io reporting for end-to-end tests. (79173)
  • Handle WP.org SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. missing tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) warnings. (79257)
  • Remove Lighthouse patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.. (79319)
  • Remove unused build:Profile-types and component-usage-stats scripts. (79113)
  • Revert “Base Styles: Add wpds-var Sass helper for design token fallbacks”. (79429)
  • Storybook: Include playground stories and MDX in CI smoke tests. (79454)
  • design-system-mcp: Remove Storybook dependency in TypeScript types. (79132)
  • devops: Configure end-to-end report auto-upload for flakiness.io dashboard. (79411)
  • devops: Upload unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. results to flakiness dashboard. (79414)

Data Layer

  • Backport changelog and package version updates from wp/latest. (79234)

Block Editor

  • Block Supports: Relocate text and bg color controls to Typography and Background panels. (77279)

Security

  • Dependabot: Add npm entry so security update PRs can be rebased. (79076)

Various

  • View configuration endpoint: Bring back changes from core. (79438)

Components

  • Icons: Self declare color. (79320)
  • Revert “Components: Complete WPDS token migration for remaining borders”. (79243)

Plugin

  • Remove ObliviousHarmony from CODEOWNERS for packages/env. (79308)

Post Editor

  • Sync editor settings in layout effect (fixes autosave e2e). (78799)

Client Side Media

  • Reconcile feature-detection docblockdocblock (phpdoc, xref, inline docs) with implemented checks. (75851)

First-time contributors

The following PRs were merged by first-time contributors:

  • @aslushnikov: Configure Flakiness.io reporting for end-to-end tests. (79173)
  • @ishitaj34: Gallery: Hide Navigation button type when lightbox editing is disabled. (79147)
  • @lonesahilnazir: Image block: Remove duplicate data-wp-bind–srcset in the lightbox overlay. (79202)
  • @sdnunca: Plugins API: Fix the plugin ‘render’ property validation. (79315)
  • @slackticus: Build: Replace Tooling unmaintained release action (78258)

Contributors

The following contributors merged PRs in this release:

@aaronrobertshaw @adamsilverstein @adamziel @aduth @andrewserong @aslushnikov @cbravobernal @chihsuan @ciampo @CookieDarb @desrosj @dhruvikpatel18 @ellatrix @fushar @hbhalodia @himanshupathak95 @i-am-chitti @im3dabasia @ishitaj34 @jameskoster @jasmussen @jordesign @jorgefilipecosta @jsnajdr @juanfra @kushagra-goyal-14 @lonesahilnazir @Mamaduka @manzoorwanijk @maxschmeling @Mayank-Tripathi32 @mcsf @mirka @Mustafabharmal @ntsekouras @oandregal @ralucaStan @ramonjd @retrofox @rushikeshmore @SainathPoojary @saulyz @scruffian @sdnunca @shail-mehta @shekharnwagh @shimotmk @shrivastavanolo @slackticus @t-hamano @taipeicoder @talldan @tellthemachines @tyxla @USERSATOSHI

Props to @wildworks, @ramonopoly, and @akirk for reviewing and providing demo videos.

#block-editor #core-editor #gutenberg #gutenberg-new

Estela Rueda 6:03 pm on July 1, 2026
Tags: 7-0-release-leads, , , ,   

WordPress 7.0.1 RC1 is now available

WordPress 7.0.1 Release Candidaterelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1 (RC1) is available for testing! Some ways you can help test this minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.:

  • Use the WordPress Beta Tester pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.
    • As this is a minor RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). release, select the Point ReleaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. channel and the Nightlies stream. This is the latest build including the RC and potentially any subsequent commits in trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision..
  • Use WP-CLI to test: wp core update https://wordpress.org/wordpress-7.0.1-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

WordPress 7.0.1 is intended as a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.-fix only maintenance release. Tickets will be included provided they are issues introduced during the 7.0 cycle or intentionally deferred at the end of the 7.0 cycle. You can follow trac report 4 or the 7.0.x editor tasks board for proposed fixes.

WordPress 7.0.1 is led by @jorbin, @cbravobernal, @estelaris and @masteradhoc

The following coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tickets are included:

  • #64318 – should not be replaced by Twemoji
  • #64742 – PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.5: Incorrect array access in `wp_get_attachment_image_src`
  • #64900 – Improve `browserslist:update` Grunt task
  • #64937 – Image editor: scale and crop input size mismatch with button and info icon not using new color
  • #64999 – Adminadmin (and super admin) reskin: Form elements are not standardized in the mobile viewport.
  • #65122 – AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) issues in Visual History
  • #65224 – Add support for testing unmerged changes from GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/
  • #65270 – wp_kses() corrupts valid CSSCSS Cascading Style Sheets. background-image: url(…) declarations into style=”)” 7.0-RC4
  • #65275 – Media Library CSS Bug: Loading spinner misaligned in media modal filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. toolbar
  • #65286 – major publishing action buttons are crowded in the Publish settings
  • #65296 – Library section under Media, search bar shifts position after searching in the WordPress admin area.
  • #65310 – Emoji detection script not being printed in admin
  • #65336 – global-styles-inline-css cannot be removed since 7.0
  • #65352 – networknetwork (versus site, blog) credit.php headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. logo for WordPress 7.0 showing broken
  • #65389 – BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Visibility: Keep hide-everywhere working after a block opts out of visibility support
  • #65418 – Previously copied files since deleted from the Gutenberg asset are persisting unexpectedly
  • #65428 – Scale button not aligned to dimensions on edit image screen.

The following Gutenberg PR are included:

  • #77530 – Visual RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.: Accessibility
  • #77750 – Block Editor: Fix blockGap fallback parsing for nested var() values.
  • #78387 – useCopyToClipboard: Always call onSuccess callback.
  • #78393 – Revisions: Use CSS outline as secondary non-color indicator for diff blocks.
  • #78426 – Image: Fix missing aria-label on lightbox trigger button for single images.
  • #78484 – Navigation: Restore block_core_navigation_submenu_render_submenu_icon() as deprecated shim.
  • #78493 – wp-build: Fix black flash on wp-admin pages before hydration.
  • #78547 – Guard PHP unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see regression. to avoid failures on old wp versions.
  • #78571 – Custom HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers.: Fix scrollbar becoming non-functional after switching tabs.
  • #79000 – Avoid dirtying related navigation entities during passive render.
  • #79048 – Navigation: Use block context to determine whether Page List is nested in Submenu.
  • #79181 – Template Part: Remove restriction on tabs / inspector fills.
  • #79350 – Mark all controlled/mode block changes non-persistent.
  • #79691 – Editor: Move focus to revisions slider when entering revisions mode.

What’s next?

Reminder: the dev-reviewed workflow (double committer sign-off) is required when making changes to the 7.0 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..

The final release is expected on Thursday, July 9, 2026. This date is subject to change if any issues with RC1 are discovered. Coordination will happen in the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ #7-0-release-leads channel, and releases are always packaged and tested in #core.

A special thanks to everyone who reported issues, helped test, and helped create patches. The success of 7.0.1 depends on proper testing, so please lend a helping hand.

Thanks to @jorbin, @cbravobernal, and @masteradhoc for pre-publication review.

#7-0, #7-0-1, #minor-releases, #releases

#minor-releases, #release

Aditya Dhade 5:49 pm on June 30, 2026
Tags: , , , ,   

Performance Chat Summary: 30 June 2026

The full chat log is available beginning here on Slack.

WordPress Performance TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets

  • @westonruter shared the current performance-focused Trac report and noted that there looks to be nothing for 7.0.1.
    • @westonruter shared that the tickets in the “Awaiting Review” queue need a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub and suggested that one could be held the following week.

Performance Lab PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. (and other performance plugins)

  • @westonruter shared that the plugin releases the team had wanted to do a couple of weeks earlier should be completed.
    • @westonruter shared that if PR #2540 can be finalized, it could be included in the release.
  • @nickchomey shared that @westonruter had reviewed a recent PR and plans to look at and address the feedback later that day.

Our next chat will be held on Tuesday, July 14, 2026 at 16:00 UTC in the #core-performance channel in Slack.

#core-performance, #hosting, #performance, #performance-chat, #summary

Amy Kamala 7:04 pm on June 22, 2026
Tags: , ,   

WordPress 7.0 Release Retrospective

A huge congratulations, and a giant thank you to everyone who helped make WordPress 7.0 happen! The release was only made possible by your dedication and hard work. You all are heroes!

Now that the development cycle is over, it’s time for a retro. You’re invited to share your thoughts on the 7.0 cycle, on processes, squad, or anything else about the release cycle. I know you all have :a lot: to say after that whirlwind, so please do! Feedback loops help uncover what is and is not working so that the release process can be improved. 

Please share your feedback using this form or by dropping a comment below. Even contributors who did not contribute directly to the release are welcome.

Someone who was simply watching the release will have thoughts and opinions that vary from someone who was more heavily involved. It’s important for diverse perspectives to be represented in feedback for big picture clarity. So no matter who you are, please speak up!

The survey is not anonymous, but submissions will be anonymized in the follow up summary. Your wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ username is only needed for any additional questions.

The form and comments will be open until July 20, 2026, and a summary of feedback will be published soon after.

Thank you for taking the time to give your valuable feedback, and thank you again for your amazing investments in 7.0 “Armstrong”. Together, future release cycles will be even better!

Props to @4thhubbard and @jeffpaul for the pre-publish review.

#7-0, #release, #release-process