The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in the bug tracker.
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 candidateOne 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.
Emcee / Release LeadRelease LeadThe community member ultimately responsible for the Release.
CommittercommitterA 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.
BetaBetaA 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
RCrelease candidateOne 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
Everyone is welcome! First-timers, veteran contributors, and all those curious about the process are invited.
The final General Release will happen during WordCampWordCampWordCamps 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.
WordPress 7.0.1 Release Candidaterelease candidateOne 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 ReleaseA 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 TesterpluginPluginA 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 candidateOne 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 ReleaseA 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 trunktrunkA 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
WordPress 7.0.1 is intended as a bugbugA 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.
#64742 – PHPPHPThe 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`
#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 – AccessibilityAccessibilityAccessibility (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 GutenbergGutenbergThe 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/
#65275 – Media Library CSS Bug: Loading spinner misaligned in media modal filterFilterFilters 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 headerHeaderThe 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 – BlockBlockBlock 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 RevisionsRevisionsThe 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
#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 testCode 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 HTMLHTMLHyperText 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.
#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 branchbranchA 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.orgThe 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/SlackSlackSlack 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.
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.orgThe 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!
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:
PluginPluginA 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 edgeThe latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “BetaBetaA 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 candidateOne 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 Download
Download the RC5 version (zip) and install it on a WordPress website.
Command Line
Use this WP-CLI command: wp core update --version=7.0–RC5
WordPress Playground
Use 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!
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 bugbugA 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.
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 betaBetaA 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)
Milestone
Emcee / Release LeadRelease LeadThe community member ultimately responsible for the Release.
CommittercommitterA 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.
@audrasjb Committing from WordCampWordCampWordCamps 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 DayContributor 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/!
RCrelease candidateOne 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
Edits: 03/10/26 Add security BetaBetaA 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 candidateOne 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.
Emcee / Release LeadRelease LeadThe community member ultimately responsible for the Release.
CommittercommitterA 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.
@audrasjb Committing from WordCampWordCampWordCamps 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 DayContributor 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/!
RCrelease candidateOne 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
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 SlackSlackSlack 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.
The forth Release Candidaterelease candidateOne 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 6.9 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 6.9 is the best it can be.
You can test WordPress 6.9 RC4 in four ways:
PluginPluginA 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 edgeThe latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “BetaBetaA 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 candidateOne 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 Download
Download the RC4 version (zip) and install it on a WordPress website.
Command Line
Use the following WP-CLI command: wp core update --version=6.9-RC4
The scheduled final release date for WordPress 6.9 is December 2, 2025. 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 6.9-related posts in the coming weeks for more information.
What’s in WordPress 6.9 RC4?
Get a recap of WordPress 6.9’s highlighted features in the Beta 1 announcement. Take a look at the WordPress 6.9 Field Guide. For more technical information related to issues addressed since RC3, you can browse the following links:
The following updates have been addressed since RC3:
#64305: Hidden async-upload field marked as required causes publishing to fail in the editor.
#64315: Running _wp_cron() during shutdown breaks sites using ALTERNATE_WP_CRON.
#64269: “Remove” button in Media Library gallery has a UIUIUser interface styling issue.
#41604:REST APIREST APIThe REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”)
https://developer.wordpress.org/rest-api/ incorrectly returns success instead of an error when updating a non-existent setting.
WordPress is open sourceOpen SourceOpen 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 6.9 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 6.9. For those new to testing, follow this general testing guide for more details on getting set up.
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 bugbugA 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.
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 6.9 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 6.9.
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.
WordPress 6.9 BetaBetaA 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 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 Beta 4 on a test server and site.
WordPress 6.9 Beta 4 can be tested using any of the following methods:
PluginPluginA 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 edgeThe latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/RCrelease candidateOne 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.)
The scheduled final release date for WordPress 6.9 is still December 2, 2025. 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!
The 6.9 Release Candidaterelease candidateOne 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). is still scheduled for Tuesday, November 11th, and the final release on December 2nd is still on track. 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 6.9 Beta 4 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 as important. This detailed guide will walk you through testing features in WordPress 6.9.
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 bugbugA 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.
WordPress 6.9 BetaBetaA 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 ready for download and testing!
This beta release is intended for testing and development only. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, use a test environment or local site to explore the new features.
How to Test WordPress 6.9 Beta 1
You can test WordPress 6.9 Beta 1 in any of the following ways:
WordPress Beta Tester PluginPluginA 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 edgeThe latest revision of the software, generally in development and often unstable. Also known as trunk.” channel and “Beta/RCrelease candidateOne 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.
Command Line (WP-CLIWP-CLIWP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/https://make.wordpress.org/cli/)
Use this WP-CLI command: wp core update --version=6.9-beta1
The scheduled final release date for WordPress 6.9 is December 2, 2025. 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 contributes by testing!
How important is your testing?
Testing for issues is a critical part of developing any software, and it’s a meaningful way for anyone to contribute—whether or not you have experience. Details on what to test in WordPress 6.9 are here.
If you encounter an issue, please share it in the Alpha/Beta area of the support forums. If you are comfortable submitting a reproducible bugbugA 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 do so via WordPress Trac. You can also check your issue against this list of known bugs.
WordPress 6.9 will include many new features that were previously only available in the GutenbergGutenbergThe 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/ plugin. Learn more about Gutenberg updates since WordPress 6.8 in the What’s New in Gutenberg posts for versions 20.4 & 20.5, 20.6 & 20.7,20.8 & 20.9,21,21.1,21.2, 21.3, 21.4, 21.5,21.6, 21.7, 21.8 & 21.9.
What’s new in WordPress 6.9?
This release brings major advancements in editing, collaboration, and developer capabilitiescapabilityA 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)..
Site Editor
Expanded Template Management: Create multiple templates per slug, draft before publishing, activate or deactivate templates as needed, and retain custom templates when switching themes.
Content Creation & Editor Features
Notes: Notes can now be attached to individual blocks. This enables asynchronous collaboration and more efficient editorial workflows. This was formerly known as ‘BlockBlockBlock 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. Comments’.
Hide Blocks on Frontend: You can hide blocks from the frontend while leaving them editable in the backend—supporting staging, alternate design explorations, and non-destructive workflows.
New Blocks: Accordion, Terms Query, Math block and Time to Read. The ‘Fit text’ formatting option is now available for paragraph and heading blocks, providing more flexibility for site building.
Drag and drop block experience: Instead of dragging a copy, users now move the actual block itself within the editor while rearranging content. The result is a visually enhanced and accessible editing experience for all users
Command Palette
Command Palette (Press Ctrl+K or Command+K anywhere in the dashboard to use the command palette) is available across both the Editor and the Dashboard, making navigation and actions faster and easier. Simply type in the Command Palette to search, jump to specific screens, or trigger actions directly. This also lays the groundwork for future integrations with the new Abilities APIAPIAn 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..
Developer & API Updates
New Abilities API: A unified registry of callable WordPress capabilities with defined inputs and outputs, built for AI integrations and developer automation.
Interactivity API Improvements: A new algorithm powers client-side navigation, enabling developers to build new user experiences that weren’t possible before and will be included in future WordPress versions, like instant search or client-side comment submissions.
DataViews & DataForm components: The release introduces support for more field types & new layouts. DataViews now offers infinite scroll for large datasets and allows for locked filters and improved multi-selection via the new DataViewsPicker.
HTMLHTMLHyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. API: These upgrades make parsing, transforming, and validating HTML safer and more efficient across blocks, site editor, and custom plugins, boosting programmatic HTML manipulation accuracy.
Block Binding API: Date block supports block bindings, image block allows binding the caption, an improved and extensibleExtensibleThis is the ability to add additional functionality to the code. Plugins extend the WordPress core software. user interface that allows custom sources in the bindings editor.
Performance
Introduced the “template enhancementenhancementEnhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. output buffer” to unlock new optimization opportunities.
Block styles loaded on demand in classic themes to reduce overall CSSCSSCascading Style Sheets. used.
Support for fetchpriority on scripts and script modules.
Support for printing script modules in the footer.
Increased inlining of stylesheets to reduce render blocking.
Minification of stylesheets in coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. block themes.
Scripts and styles for hidden blocks omitted by default.
Emoji detection script converted to a script module and moved to footer.
Database query optimizations and caching.
Cron spawned at shutdown instead of init to reduce impact on TTFB.
Improvements to RSS feedRSS FeedRSS is an acronym for Real Simple Syndication which is a type of web feed which allows users to access updates to online content in a standardized, computer-readable format. This is the feed. caching.
UTF-8 processing optimizations.
Additional Notes
No new default theme in 6.9: There is no bundled theme shipping with 6.9; the focus is on enhancing the editor experience, API support and performance.
Early Preview Plugins: MCP Adapter, and PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher AI Client are launching as canonical packages and plugins alongside 6.9, but are not part of Core.
The MCP Adaptor turns WordPress Abilities into MCP Tools that can be used by AI agents.
The PHP AI Client allows WordPress to connect to LLMS for AI powered content creation.
Just for you: a Beta 1 haiku
Beta moon arises, In its glow, we debug dreams— Stable stars ahead.
This post aims to prepare a calendar with the expected start time for each release party and who is involved in the upcoming 6.9 milestone.
The release party schedule will remain unchanged during the Release Candidaterelease candidateOne 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 for the final release of WordPress 6.9. This allows 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.
Emcee / Release LeadRelease LeadThe community member ultimately responsible for the Release.
CommittercommitterA 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.
BetaBetaA 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
RCrelease candidateOne 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
