WordPress 7.1.1 RC1 is now available

WordPress 7.1.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.1.1-RC1.zip
  • Directly download the Beta/RC version.

What’s in this release candidate?

WordPress 7.1.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.1 cycle or intentionally deferred at the end of the 7.1 cycle. You can follow trac report 4 or the 7.1.x editor tasks board for proposed fixes.

WordPress 7.1.1 is led by @adamsilverstein, @adrianduffell, and @andraganescu.

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

  • #66001 – Accessing /wp-adminadmin (and super admin)/admin-post.php?page=font-library while logged loads Site Editor
  • #65929BlockBlock 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. Supports: Bail early in wp_render_block_states_support() when a block has no style attribute
  • #65674 – Tooltip Delay Timer Race Condition (wp-includes/js/wp-tooltip.js)
  • #65943 – wp-tooltip 7.1 bug
  • #65914 – wp_get_tooltip() treats custom button markup as a sprintf() format string
  • #65918 –  Tooltip icon is not aligned with “Remember Me” text in login box
  • #66056 – Media: prepare the attachment finalize response from the current post row
  • #65922regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5.: client-side processing creates thumbnails larger than original for indexed PNG images
  • #66012Multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site: reassign dropdown missing when deleting a user, silently destroying content (7.1 regression)
  • #65919 – Array keys in WP_Hook::$callbacks may now be integers instead of strings in 7.1 causing fatal errors with string functions
  • #65985 – Plugins: In < 782px screens paused plugins has two left borders
  • #65956 – Mobile layout breaks on post list table during plugin update
  • #65945 – Native sitemap is served with a 404 status on sites with no published posts
  • #66044 – spacing.blockGap in a block style variation stops emitting any gap
  • #66064 – Site icon in the Admin Bar (Toolbar) sits atop the site title when using a tablet in portrait orientation
  • #65924 – Set Site Icon background color to transparent

The following 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/ PRs are included:

  • #81770 – Block Editor: Add translator context to pseudo-state labels
  • #81813 – Fix: Post Editor: 403 on /wp/v2/settings at boot for users without manage_options cap
  • #82046 – Media: Refuse a multi-file drop on a placeholder that takes one file
  • #82011 – List: outdent an empty middle item without adding an item
  • #81782 – Accordion Panel: Reset padding-block when panel is hidden
  • #81964 – List View: Don’t focus the last Table cell on keyboard activation
  • #81397 – Media: Stop claiming “Upload complete” when every upload failed
  • #81884 – Media: keep indexed PNG sub-sizes indexed
  • #82316 – Image block cropping: Sync image size and link destination settings
  • #82318 – Gallery block: Fix ‘Crop images to fit’ broken in editor
  • #82254 – Pages: require authentication and a capabilitycapability 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). to render generated standalone pages
  • #82353 – Media Utils: Preserve arrays in multipart form data
  • #82478 – wp-env: Fix Docker build errors with Debian Bullseye repositories
  • #82465 – Query LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop: Fall back to post when the query has no postType
  • #81908 – Block Supports: Bail early in state styles when a block has no style attribute
  • #82335 – Fix: Restore layout styles for block style variations
  • #81947 – Editor: Store the finalize response as the attachment record
  • #82265 – Media: Only blame the browser’s codecs when HEIC really cannot be decoded
  • #82249 – CI: Unify the automation comments into a single PR comment
  • #82183 – useViewConfig: don’t request the view config twice
  • #82635 – Framework: Update Node.js to v24 LTS and npm to v11

What’s next?

Reminder: the dev-reviewed workflow (double committer sign-off) is required when making changes to the 7.1 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, September 17, 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-1-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.1.1 depends on proper testing, so please lend a helping hand.

Thanks to @andraganescu and @adamsilverstein for pre-publication review.

#7-1, #7-1-1, #minor-releases, #release

WordPress 7.1 Release Retrospective

A huge congratulations, and a giant thank you to everyone who helped make WordPress 7.1 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.1 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 by September 30th. 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 September 30, 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.1 “Mary Lou”. Together, future release cycles will be even better.

Props to @krupajnanda and @annezazu for the pre-publish review.

#7-1, #release, #release-process

WordPress 7.1 Release Candidate 4

The fourth 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). (“RC4”) for WordPress 7.1 is ready for download and testing!

This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC4 on a test server and site.

Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 7.1 is the best it can be.

You can test WordPress 7.1 RC4 in four ways:

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.Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “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./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). Only” stream).
Direct DownloadDownload the RC4 version (zip) and install it on a WordPress website.
Command LineUse the following WP-CLI command: wp core update --version=7.1-RC4
WordPress PlaygroundUse the 7.1 RC4 WordPress Playground instance to test the software directly in your browser without the need for a separate site or setup.

The scheduled final release date for WordPress 7.1 is August 19, 2026. The full release schedule can be found here. Your help testing RC versions is vital to making this release as stable and powerful as possible.

Please continue checking the Make WordPress Core blog for 7.1-related posts for more updates and information.

What’s in WordPress 7.1 RC4?

WordPress 7.1 RC4 contains more than 26 updates and fixes since the RC3 release, including 8 in the Editor and 18 in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

Want to look deeper into the details and technical notes for this release? Take a look at the WordPress 7.1 Field Guide. For technical information related to issues addressed since WordPress 7.1 RC1 release, you can browse the following links:

How you can contribute

WordPress is open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.

Get involved in testing

Testing for issues is crucial to the development of any software. It’s also a meaningful way for anyone to contribute. 

Your help testing the WordPress 7.1 RC4 version is key to ensuring that the final release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This detailed guide will walk you through testing features in WordPress 7.1.

If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible 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. report.  You can also check your issue against a list of known bugs

Curious about testing releases in general?  Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

Update your theme or plugin

For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.

Thanks for continuing to test your themes and plugins with the WordPress 7.1 beta releases. If you haven’t yet, make sure to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 7.1

If you find compatibility issues, please post detailed information to the support forum.

Test on your hosting platforms

Web hosts provide vital infrastructure for supporting WordPress and its users. Testing on hosting systems helps inform the development process while ensuring that WordPress and hosting platforms are fully compatible, free of errors, optimized for the best possible user experience, and that updates roll out to customer sites without issue.

Want to test WordPress on your hosting system? Get started with configuring distributed hosting tests here

Help translate WordPress

Do you speak a language other than English? ¿Español? Français? Русский? 日本語? हिन्दी? বাংলা? मराठी? ಕನ್ನಡ?  You can help translate WordPress into more than 100 languages. This release milestone (RC4) also marks the hard string freeze point of the 7.1 release cycle.

An RC4 haiku

The code goes quiet,
we run it through once for real—
Phoenix waits ahead.

Props to @amykamala, @krupajnanda, @wildworks and @annezazu for proofreading and review.

#7-1, #development, #release

WordPress 7.1 Release Candidate 3

Note: This post has been published on Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. in light of the WordPress 7.0.4 security release. You can read more about the security release.
WordPress 7.1 RC2 was released on August 6, 2026, as part of the WordPress 7.0.3 security release.

The third 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). (“RC3”) for WordPress 7.1 is ready for download and testing!

This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC3 on a test server and site.

Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 7.1 is the best it can be.

You can test WordPress 7.1 RC3 in four ways:

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.Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “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./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). Only” stream).
Direct DownloadDownload the RC3 version (zip) and install it on a WordPress website.
Command LineUse the following WP-CLI command: wp core update --version=7.1-RC3
WordPress PlaygroundUse the 7.1 RC3 WordPress Playground instance to test the software directly in your browser without the need for a separate site or setup.

The scheduled final release date for WordPress 7.1 is August 19, 2026. The full release schedule can be found here. Your help testing RC versions is vital to making this release as stable and powerful as possible.

Please continue checking the Make WordPress Core blog for 7.1-related posts for more updates and information.

What’s in WordPress 7.1 RC3?

WordPress 7.1 RC3 contains more than 90 updates and fixes since the RC1 release, including 37 in the Editor and 57 in Core.

Want to look deeper into the details and technical notes for this release? Take a look at the WordPress 7.1 Field Guide. For technical information related to issues addressed since WordPress 7.1 RC1 release, you can browse the following links:

How you can contribute

WordPress is open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.

Get involved in testing

Testing for issues is crucial to the development of any software. It’s also a meaningful way for anyone to contribute. 

Your help testing the WordPress 7.1 RC3 version is key to ensuring that the final release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This detailed guide will walk you through testing features in WordPress 7.1.

If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible 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. report.  You can also check your issue against a list of known bugs

Curious about testing releases in general?  Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

Update your theme or plugin

For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.

Thanks for continuing to test your themes and plugins with the WordPress 7.1 beta releases. If you haven’t yet, make sure to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 7.1

If you find compatibility issues, please post detailed information to the support forum.

Test on your hosting platforms

Web hosts provide vital infrastructure for supporting WordPress and its users. Testing on hosting systems helps inform the development process while ensuring that WordPress and hosting platforms are fully compatible, free of errors, optimized for the best possible user experience, and that updates roll out to customer sites without issue.

Want to test WordPress on your hosting system? Get started with configuring distributed hosting tests here

Help translate WordPress

Do you speak a language other than English? ¿Español? Français? Русский? 日本語? हिन्दी? বাংলা? मराठी? ಕನ್ನಡ?  You can help translate WordPress into more than 100 languages. This release milestone (RC3) also marks the hard string freeze point of the 7.1 release cycle.

An RC3 haiku

Small cracks catch the light,
We polish, not propose—
Almost ready now.

Props to @benjamin_zekavica, @amykamala, @wildworks and @annezazu for proofreading and review.

#7-1, #development, #release

WordPress 7.1 Release Party Schedule

WordPress 7.1 is scheduled for release on August 19, 2026! Below is the proposed calendar with expected start times for each release party, and the release squad contributors involved in release parties for the upcoming 7.1 milestone.

This release party schedule will stay in effect during the 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). phase and the final release of WordPress 7.1. This enables contributors to attend and assist with release testing during the final weeks of the release cycle.

As always, there may be last-minute adjustments. The release squad will do its best to communicate any changes promptly by publishing a post on the change, and updating this post as the canonical reference.

Join us for the 7.1 release parties in the #core channel on the Making WordPress Slack!

Release Schedule

Date (UTC)MilestoneEmcee / Release LeadRelease Lead The community member ultimately responsible for the Release.Committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.SecurityMission Control (Coordination)
July 15, 2026 at 15:00 UTCBeta 1@krupajnanda@wildworks@joedolson@sergeybiryukov
July 17, 2026Beta 2@johnbillion
July 22, 2026 at 15:00 UTCBeta 3@krupajnanda@wildworks@joedolson@sergeybiryukov
July 29, 2026 at 15:00 UTCBeta 4@benjamin_zekavica@wildworks@joedolson@sergeybiryukov
August 5, 2026 at 15:00 UTCRC 1@benjamin_zekavica@wildworks@joedolson@desrosj
August 6, 2026RC 2@johnbillion
August 12, 2026 at 15:00 UTCRC 3@krupajnanda@wildworks@joedolson@sergeybiryukov
August 17, 2026 at 15:00 UTCDry Run / 24-Hour Code Freeze@krupajnanda@wildworks@joedolson@sergeybiryukov
Part 1 | Release Party:
August 19, 2026 at 19:45 UTC

Part 2 | Release Announcement:
August 19, 2026 at 23:10 UTC
General Release@benjamin_zekavica
@amykamala
@wildworks@joedolson@sergeybiryukov

How to Join the Party

  • All parties happen in the #core channel on Slack.
  • Everyone is welcome! First-timers, veteran contributors, and all those curious about the process are invited.
  • The final General Release will happen during WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US 2026.
  • Everyone is encouraged to attend WordCamp US, but traveling and attending the event is not required to participate in the General Release Party. The release party will still happen in the #core channel on Slack.

Here are detailed instructions on how to contribute to a release party.

Thank you to every contributor and community member that helps make 7.1 a success. See you at the parties!

UPDATE (17 July 2026): Beta 2 was updated to today due to the unplanned 7.0.2 release, all other 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. and 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). releases will continue as planned with an extra beta for this release.

Props to @krupajnanda and @amykamala for collaboration and peer review, @jeffpaul for the 7.0.2 update.

#7-1, #release

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
  • #64742PHPPHP 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
  • #64999Adminadmin (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
  • #65389BlockBlock 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

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

WordPress 7.0 Release Candidate 5

WordPress 7.0 RC5 is ready for download and testing!

This version of the WordPress software is still under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended to test RC5 on a test server and site.

WordPress 7.0 RC5 can be tested using any of the following methods:

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.Install and activate the WordPress Beta Tester plugin on a WordPress install. (Select the “Bleeding edgebleeding edge The latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “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./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). Only” stream.)
Direct DownloadDownload the RC5 version (zip) and install it on a WordPress website.
Command LineUse this WP-CLI command: wp core update --version=7.0–RC5
WordPress PlaygroundUse the WordPress Playground instance to test the software directly in your browser.  No setup is required – just click and go! 

The scheduled final release date for WordPress 7.0 May 20, 2026. The full release schedule can be found here. Your help testing Beta and RC versions is vital to making this release as stable and powerful as possible. Thank you to everyone who helps with testing!

Please continue checking the Make WordPress Core blog for 7.0-related posts in the coming weeks for more information. 

What’s new in WordPress 7.0? Check out the Field Guide for details and highlights.

This is an extra RC

Testing for issues is critical to the development of any software, and testing works!

This RC is being released to test changes prior to the final release of 7.0.

You can browse the technical details for all issues addressed since Beta 5 using these links:

The 7.0 release is scheduled for Wednesday, May 20th. As always, a successful release depends on your confirmation during testing. So please download and test!

How to test this release

Your help testing the WordPress 7.0 RC5 version is key to ensuring that the final release is the best it can be. While testing the upgrade process is essential, trying out new features is equally important. This detailed guide will walk you through testing features in WordPress 7.0.

If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible 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. report. You can also check your issue against a list of known bugs.

Curious about testing releases in general? Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

A RC5 haiku

Gift for everyone

RC5 shines like the sun

Test it and have fun

Props to @sergeybiryukov, @huzaifaalmesbah for proofreading and review.

#7-0, #development, #release

WordPress 7.0 Release Party Updated Schedule

Good news, everyone! WordPress 7.0 has a new release date: May 20th, 2026!

Thank you all for your flexibility in these recent weeks while WordPress contributors around the world worked tirelessly on necessary architectural improvements for the 7.0 release. The team aims to ensure that this software version is the most stable and most performant it can be, while still delivering the much anticipated cornerstone features mapped out for WordPress 7.0.

Below is the new release schedule, with expected dates and times for each release party, and the release squad contributors involved in each party for the 7.0 milestone. It also includes the pre-release versions that have already been released, and a (pending) call for testing from web hosts meant to help ensure compatibility across hosting systems.

Note: While the most recent pre-release version was RC2, the RC3 release will be treated like a 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. version in practice. That means that your continued testing and feedback, particularly on the part of web hosts, will be incredibly valuable in keeping the development process informed during the next phase of this release cycle. Thank you all for your continued testing!

Release Schedule

As always, last-minute adjustments to this schedule are possible, and there could be additional timeline iterations based on the impact of host feedback to ensure that feedback is properly addressed. The release squad will do its best to communicate any changes promptly by posting in the #core Slack channel, publishing a post on the change, and updating this post as the canonical reference.

Date (UTC)MilestoneEmcee / Release LeadRelease Lead The community member ultimately responsible for the Release.Committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.SecurityMission Control (Coordination)
February 19, 2026 at 15:00 UTCBeta 1@amykamala@ellatrix@audrasjb@sergeybiryukov
February 26, 2026 at 15:00 UTCBeta 2@amykamala@ellatrix@audrasjb@sergeybiryukov
March 5, 2026 at 14:00 UTC Beta 3@amykamala@audrasjb
Committing from WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Nice Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/!
@audrasjb@sergeybiryukov
March 10, 2026 at 23:30 UTC
Unplanned beta following the 6.9.2-6.9.3 security releases
Beta 4@desrosj@sergeybiryukov@sergeybiryukov@sergeybiryukov
March 12, 2026 at 15:00 UTCBeta 5@chaion07@ellatrix@audrasjb@sergeybiryukov
March 24, 2026 at 15:00 UTCRCrelease 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@amykamala@ellatrix@audrasjb@sergeybiryukov
March 26, 2026 at 15:00 UTCRC 2@4thhubbard@ellatrix@audrasjb@sergeybiryukov
April 24, 2026Call for host testing@desrosjn/an/an/a
May 8, 2026 at 15:00 UTCRC 3 (in name, but test as a “new Beta 1”)@amykamala@ellatrix@audrasjb@sergeybiryukov
May 14, 2026 at 15:00 UTCRC 4 (in name, but acting as a “new RC1”)@4thhubbard @chaion07@ellatrix@audrasjb@sergeybiryukov
Tuesday, May 19, 2026 at 15:00 UTC

Dry Run / 24-Hour Code FreezeTBDTBDTBDTBD
Wednesday, May 20, 2026

Time TBA
General ReleaseTBDTBDTBDTBD

How to Join the Party

  • All parties happen in the #core channel on Slack.
  • Everyone is welcome! First-timers, veteran contributors, and all those curious about the process are invited.

Here are detailed instructions on how to contribute to a release party.

Thank you to every contributor and community member that helps make 7.0 a success. See you at the parties!

Props to @desrosj, @4thhubbard, @annezazu, @griffbrad,@peterwilsoncc, and @jeffpaul for helping devise the new schedule, and @desrosj, @jeffpaul, and @sumitsingh for reviewing this post.

#7-0, #release

WordPress 7.0 Release Party Schedule

Note: This schedule is no longer current. The new schedule can be found here.

Edits: 03/10/26 Add security 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. 4, 3/19/26 Update date for RC1, 4/5/26 Update to reflect delay

WordPress 7.0 is scheduled for release on April 9, 2026! Below is the proposed calendar with expected start times for each release party, and the release squad contributors involved in release parties for the upcoming 7.0 milestone.

This release party schedule will stay in effect during the 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). phase and the final release of WordPress 7.0. This enables contributors to attend and assist with release testing during the final weeks of the release cycle.

As always, there may be last-minute adjustments. The release squad will do its best to communicate any changes promptly by publishing a post on the change, and updating this post as the canonical reference.

Join us for the 7.0 release parties in the #core channel on the Making WordPress Slack!

Release Schedule

Date (UTC)MilestoneEmcee / Release LeadRelease Lead The community member ultimately responsible for the Release.Committercommitter A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component.SecurityMission Control (Coordination)Communications
February 19, 2026 at 15:00 UTCBeta 1@amykamala@ellatrix@audrasjb@sergeybiryukov@amykamala
February 26, 2026 at 15:00 UTCBeta 2@amykamala@ellatrix@audrasjb@sergeybiryukov@amykamala
March 5, 2026 at 14:00 UTC Beta 3@4thhubbard, @amykamala@audrasjb
Committing from WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Nice Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/!
@audrasjb@sergeybiryukov@4thhubbard
March 10, 2026 at 23:30 UTC
Unplanned beta following the 6.9.2-6.9.3 security releases
Beta 4@desrosj@sergeybiryukov@sergeybiryukov@sergeybiryukov
March 12, 2026 at 15:00 UTCBeta 5@chaion07, @amykamala@ellatrix@audrasjb@sergeybiryukov@chaion07
March 24, 2026 at 15:00 UTCRCrelease 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@amykamala@ellatrix@audrasjb@sergeybiryukov@amykamala
March 26, 2026 at 15:00 UTCRC 2@4thhubbard@ellatrix@audrasjb@sergeybiryukov@4thhubbard
April 2, 2026 at 15:00 UTC

Delayed: Time & Date TBA
RC 3@chaion07@ellatrix@audrasjb@sergeybiryukov@chaion07
Wednesday, April 8, 2026.

Delayed: Time & Date TBA
Dry Run / 24-Hour Code FreezeTBDTBDTBDTBDTBD
Thursday, April 9, 2026. Live during WordCamp Asia 2026 Contributor Day!

Delayed: Time & Date TBA
General ReleaseTBDTBDTBDTBDTBD

How to Join the Party

  • All parties happen in the #core channel on Slack.
  • Everyone is welcome! First-timers, veteran contributors, and all those curious about the process are invited.
  • The final General Release will happen during WordCamp Asia 2026 Contributor Day.
  • Everyone is encouraged to attend WordCamp Asia, but traveling and attending the event is not required to participate in the General Release Party. The release party will still happen in the #core channel 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/.
  • @desrosj is leading the coordination between the release squad and WordCamp Asia organizing team for the Dry Run and General Release schedules. More details will be announced as soon as they are finalized.

Here are detailed instructions on how to contribute to a release party.

Thank you to every contributor and community member that helps make 7.0 a success. See you at the parties!

Props to @desrosj, @4thhubbard, @jeffpaul, @chaion07, @audrasjb, @sergeybiryukov, @ellatrix, and @akshayar for collaboration and peer review.

#7-0, #release