WordPress 6.0 Release Candidate 3 (RC3) Now Available for Testing

WordPress 6.0 is scheduled for release next week on May 24, 2022! This RC3 release is the final opportunity for you to test and help contribute to making the 6.0 release great.

You can view changes since the RC2 release via Gutenberg and Trac.

Installing RC3

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

You can test WordPress 6.0 RC3 in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the release candidate (zip).

Option 3: When using WP-CLI to upgrade from Beta 1, 2, 3, 4, RC1, or RC2 on a case-insensitive filesystem, please use the following command:

wp core update --version=6.0-RC3

Plugin and Theme Developers

All plugin and theme developers are encouraged to complete testing of their respective extensions against WordPress 6.0 RC3 and update the “Tested up to” version in their readme file to 6.0 this week. If you find compatibility problems, please be sure to post detailed information to the support forums, so these items can be investigated further prior to the final release date of May 24.

Review the WordPress 6.0 Field Guide, for more details on this release.

Review additional information on the full 6.0 release cycle.

Check the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail upcoming changes.

Translate WordPress

Do you speak a language other than English? Help translate WordPress into more than 100 languages.

How to Help Test WordPress

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.

If you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.


RC3, An (Almost) Final Haiku

It’s near time for six
The reward is the journey
Just one week to go


Thank you to the following contributors for collaborating on this post: @dansoschin, @webcommsat

WordPress 6.0 Release Candidate 2 (RC2) Now Available for Testing

The next release candidate for WordPress 6.0 is now available! 

WordPress 6.0 is scheduled for release on May 24th, 2022 – just two weeks from today.

“Release Candidate” means that this version of WordPress is ready for release! Since the WordPress ecosystem includes thousands of plugins and themes, it is important that everyone within the WordPress community check to see if anything was missed along the way. That means the project would love your help.

Thank you to everyone who has contributed towards testing and logging issues to help make WordPress 6.0 stable (and awesome). WordPress still needs your help testing, especially theme and plugin developers.

Since the RC1 release on May 3rd, 2022, there have been approximately 40 issues resolved in Gutenberg and Trac.

Installing RC2

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

You can test WordPress 6.0 RC2 in three ways:

  • Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).
  • Option 3: When using WP-CLI to upgrade from Beta 1, 2, 3, 4, or RC1 on a case-insensitive filesystem, please use the following command:
    wp core update --version=6.0-RC2

Additional information on the full 6.0 release cycle is available here.

Check the Make WordPress Core blog for 6.0-related developer notes in the coming weeks, which will detail all upcoming changes.

Plugin and Theme Developers

All plugin and theme developers should test their respective extensions against WordPress 6.0 RC2 and update the “Tested up to” version in their readme file to 6.0. If you find compatibility problems, please be sure to post detailed information to the support forums so that these items can be investigated further prior to the final release date of May 24th.

Review the WordPress 6.0 Field Guide for more details on this release.

Translate WordPress

Do you speak a language other than English? Help translate WordPress into more than 100 languages.

How to Help Test WordPress

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.

If you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.


An RC2 Haiku for You

Anticipation
Sprinting toward G/A now
Please — test, translate — thanks!


Thank you to the following contributors for collaborating on this post: @dansoschin, @priethor.  

WordPress 6.0 Release Candidate 1

The first release candidate (RC1) for WordPress 6.0 is now available!

This is an important milestone on the 6.0 release cycle journey. “Release Candidate” means that this version of WordPress is ready for release! Before the official release date, time is set aside for the community to perform final reviews and help test. Since the WordPress ecosystem includes thousands of plugins and themes, it is important that everyone within the WordPress community check to see if anything was missed along the way. That means the project would love your help.

WordPress 6.0 is planned for official release on May 24th, 2022, three weeks from today. 

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

You can test WordPress 6.0 RC1 in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the release candidate version here (zip).

Option 3: When using WP-CLI to upgrade from Beta 1, 2, 3, or 4, on a case-insensitive filesystem, please use the following command sequence:

Command One:
wp core update --version=6.0-RC1

Command Two:
wp core update --version=6.0-RC1 --force

Additional information on the full 6.0 release cycle is available here.

Check the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail all upcoming changes.

What’s in WordPress 6.0 RC1?

Since Beta 4, various items have been addressed, including (but not limited to): 

  • Backport updates of Comment blocks tests (#55643)
  • Backport a bugfix of Comment Template block pagination (#55658)
  • Editor: Backport bug fixes for WordPress 6.0 from Gutenberg (#55567)

WordPress 6.0 is the second major release for 2022, following 5.9 which became generally available in January. This release includes nearly 1,000 fixes and enhancements spanning most areas of the WordPress platform. Some key highlights within the content creation and site-building feature sets include:

  • Style Switching: switch up the look and feel of your site, all in one block theme. No need to change themes!
  • More template options: use blocks to edit five more templates (author, date, categories, tag, and taxonomy).
  • Multi-select: Easily select text across multiple blocks. Edit to your liking.
  • Retain Styles: Keep your custom styles in place, whether transforming between blocks or creating new buttons. 
  • More patterns in more places: the Quick Inserter surfaces patterns that might work well for the condition you’re in, baking in relevant patterns for template parts and pages you’re working on. 
  • List View improvements: New keyboard shortcuts (shift + click) let you select multiple blocks to modify in bulk (reposition, delete, etc.), see your content at a glance with a collapsed by default view, and more.
  • Refined design tools: Explore a new color panel, transparency options, more group block variations to create new layout options (Stack, Row), the ability to set your featured image in a Cover block, control the exact size of your featured image, gap support for the Gallery block, and more.
  • New blocks: Various Post Comments, Read More, No Results in Query Loop, Post Author Biography, Avatar blocks. 
  • Block Locking: Choose to disable the option to remove a block, move it, or both, right in the editor. 
  • Export block themes: Explore the improved block theme export tool, as WordPress heads closer to codeless visual block theme building.

Plugin and Theme Developers

All plugin and theme developers should test their respective extensions against WordPress 6.0 RC1 and update the “Tested up to” version in their readme file to 6.0. If you find compatibility problems, please be sure to post detailed information to the support forums, so these items can be investigated further prior to the final release date of May 24th.

Review the WordPress 6.0 Field Guide, for more details on what’s contained in this release.

Translate WordPress

Do you speak a language other than English? Help translate WordPress into more than 100 languages. This release also marks the hard string freeze point of the 6.0 release cycle.

How to Help Test WordPress

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.

If you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.


Haiku Fun for RC 1

Release candidate 
Our journey nearly done
Get ready, WordPress


Thank you to the following contributors for collaborating on this post: @dansoschin, @webcommsat, and @annezazu.

WordPress 6.0 Beta 4

WordPress 6.0 Beta 4 is now available for testing!

Beta 4 was not part of the originally published development cycle. It is aimed at providing an opportunity for testing some specific issues that were resolved since Beta 3. WordPress will continue with the regularly scheduled release milestones on May 3rd, 2022, with the RC1 release.

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

You can test WordPress 6.0 Beta 4 in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the beta version here (zip).

Option 3: Use WP-CLI to test: wp core update –version=6.0-beta4.
Do not use this option if your filesystem is case-insensitive.

The current target for the final 6.0 release is May 24, 2022, which is in less than a month! 

Additional information on the full 6.0 release cycle is available.

Check the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail all upcoming changes.

Explore What’s in Beta 4

Since Beta 3, various items have been addressed, including (but not limited to): 

  • Update post content placeholder (#40177)
  • Comments block: Fix glitches found while backporting (#40628)
  • Show add pattern label when patterns are being prioritised (#40598)
  • Fix regression with featured images in latest posts (#40662)
  • Navigation Link: Avoid unnecessary re-renders (#40696)
  • Navigation: Improve selector performance (#40700)
  • Comments Title: Count toggle working in ‘Singular’ editing mode (#40728)
  • [Writing Flow]: Try to fix multi-selection with shift+click (#40687)
  • Fix alignment issue with comment author name (#40610)
  • Comment Content: Show moderation message (#40612)
  • Display paragraph breaks in comment contents block (#40667)
  • Fix style comment awaiting moderation indentation (#40681)
  • Fix: Page patterns don’t show when only one pattern is available (#40707)
  • Update the placeholder for post excerpt (#40178)
  • REST API: Fix regression in the Pattern Directory endpoint. (#55617)
  • REST API: Fix the scheme for the Block Directory search endpoint. (#53621)
  • Show comments previews in the Comment Query Loop. (#55634)
  • Avoid DB error in comment meta queries. (#55218)

How to Help

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.

If you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.


Another Haiku, Just for You

Beta four, surprise!
Iterating all day long
Time to share and test


Thank you to the following contributors for collaborating on this post:
@dansoschin, @annezazu, and @costdev

WordPress 6.0 Beta 3

WordPress 6.0 Beta 3 is now available for testing!

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

You can test WordPress 6.0 Beta 3 in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the beta version here (zip).

Option 3: Use WP-CLI to test: wp core update --version=6.0-beta3.
Do not use this option if your filesystem is case-insensitive.

The current target for the final 6.0 release is May 24, 2022, which is in less than a month! 

Additional information on the full 6.0 release cycle is available here.

Check the Make WordPress Core blog for 6.0-related developer notes in the coming weeks which will detail all upcoming changes.

See What’s in Beta 3

Since Beta 2, various items have been addressed, including (but not limited to): 

  • Twenty Twenty-Two: Implement alternate json files #55433
  • Fix duotone rendering in site editor #37727 
  • Create Comments Title block with simple styling #40419 
  • Navigation block: After choosing an option from Select Menu, focus after block render #40390
  • Add comment id to all comments inside comments query loop #40268
  • Add post-comments-form block to comments template #40256
  • Elements: Add styles to the footer before the block is rendered #37728
  • Add default comment status to discussion settings  #55567
  • Fix styles for nested elements (link color) #55567
  • Move wp_enqueue_block_style() to wp-includes/script-loader.php, for better consistency #55182, #55148
  • Move administration related hooks to admin-filters.php #54795

Update on the Webfonts API and Style Variations in Twenty Twenty-Two

A prior announcement for WordPress 6.0 Beta 1 included a reference to “Webfonts API: Manage local fonts with PHP or theme.json”, as a feature that would be included in the release. WordPress 6.0 Beta 3 will allow theme authors to use webfonts in theme.json, with a public API for plugins to register and enqueue webfonts available in a future version for WordPress. Beta 3 will also include three new style variations to the Twenty Twenty-Two default theme.

How to Help

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.

If you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.


Thank you to the following contributors for collaborating on this post: @dansoschin  @webcommsat, @audrasjb


And now another WordPress haiku:

Release day is near
6.0 abounds with joy
New features soon here

WordPress 6.0 Beta 2

WordPress 6.0 Beta 2 is now available for testing!

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

You can test the WordPress 6.0 Beta 2 in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the beta version here (zip).

Option 3: Use WP-CLI to test: wp core update --version=6.0-beta2
Do not use this option if your filesystem is case-insensitive.

The current target for the final release is May 24, 2022, which is about five weeks away. 

Additional information on the full 6.0 release cycle is available.

Check the Make WordPress Core blog for 6.0-related developer notes in the coming weeks, which will detail all upcoming changes.

What’s New In Beta 2

As a reminder, contributors have fixed 209 tickets in WordPress 6.0, including 110 new features and enhancements. Each beta cycle focuses on bug fixes, and more are on the way with your help through testing. Here are a few of the changes you will find in Beta 2 specifically: 

  • Block Editor: Prevent styles from being added to the site editor (#55567)
  • Patterns REST API: Add ‘inserter’ to the schema  (#55567)
  • Don’t load remote patterns twice in WP_REST_Block_Patterns_Controller::get_items (#55567)
  • Add the ability to filter the whole notification email in retrieve_password (#54690)
  • Avoid translating empty plugin headers (#54586)

Note on Webfonts API

Last week’s announcement for WordPress 6.0 Beta 1 includes a reference to “Webfonts API: Manage local fonts with PHP or theme.json,” as a feature that would be included in the release. This specific functionality was not included in Beta 2 but may be available at RC.

How to Help

Testing for issues is critical for stabilizing a release throughout its development. Testing is also a great way to contribute to WordPress. If you are new to testing, check out this detailed guide that will walk you through how to get started.

If you think you have run into an issue, please report it to the Alpha/Beta area in the support forums. If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac. This is also where you can find a list of known bugs.


Thank you to the following contributors for collaborating on this post: @dansoschin, @annezazu, @costdev, @priethor


And now a WordPress Haiku:

We code fervently

A breathless pause for the test

‘Collaborative community’ to the rescue

Key tapping resumes

WordPress 5.9 RC3

The third Release Candidate (RC3) for WordPress 5.9 is here!

Thank you to everyone who has contributed thus far toward testing and filing bugs to help make WordPress 5.9 a great release. WordPress 5.9 is slated to land in just one week—on January 25, 2022. You still have time to help! Since RC2 arrived last week, testers have found and fixed two bugs, 14 fixes from Gutenberg. There has been one additional Gutenberg fix today.

Testing the release

You can test the WordPress 5.9 release candidate in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Download the beta version here (zip).

Option 3: When using WP-CLI to upgrade from Beta 1, 2, 3, 4, RC1, or RC2 on a case-insensitive filesystem, please use the following command sequence:

Command One:

wp core update --version=5.9-RC3

Command Two:

wp core update --version=5.9-RC3 --force

Your help to test the third Release Candidate is vital: the more testing that happens, the more stable the release, and the better the experience for users, developers, and the WordPress community.

Thank you to all contributors who tested the RC2 release and gave feedback. Testing for bugs is a critical part of polishing every release and is a great way to contribute to WordPress.

How to help

Help test WordPress 5.9 features – this post provides a guide to set up your testing environment, a list of testable features, and information about how to submit feedback you find as you go.

Skilled in languages other than English? Help translate WordPress into more than 100 languages! Thanks to every locale that is working on translations.

Developers and those interested in more background to the features can find more in the Field Guide. You can also follow the 5.9 development cycle and timeline.

If you have found a bug, you can post the details to the Alpha/Beta area in the support forums.

If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac, where you can also check the issue against a list of known bugs.

For their help in compiling this post, props to @cbringmann, @webcommsat, @psykro,@marybaum, @chanthaboune, @davidbaumwald, and @hellofromtonya.

WordPress 5.9 RC 2

The second Release Candidate (RC2) for WordPress 5.9 is now available! 

“Release Candidate” means the new version of the software is ready for release. It helps the community check that nothing is missed, given the thousands of plugins and themes and differences in how millions of people use the software.

Thank you to everyone who has contributed thus far towards testing and filing bugs to help make WordPress 5.9 a great release. WordPress 5.9 is slated for release in just two weeks on January 25, 2022. There’s still time to help! Since RC1 was released, six bugs have been found and fixed. There were 13 bug fixes backported from Gutenberg.

Testing the release

You can test the WordPress 5.9 release candidate in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the beta version here (zip).

Option 3: When using WP-CLI to upgrade from Beta 1, 2, 3, 4, or RC1, on a case-insensitive filesystem, please use the following command sequence:

Command One:

wp core update --version=5.9-RC2

Command Two:

wp core update --version=5.9-RC2 --force

Your help to test the second Release Candidate is vital: the more testing that happens, the more stable the release, and the better the experience for users and developers—and the entire WordPress community.

Thank you to all of the contributors who tested the RC1 release and gave feedback. Testing for bugs is not just a critical part of polishing every release, it is also a great way to contribute to WordPress.

How to Help

Help test WordPress 5.9 features – a guide to how you can take part.

Can you write in another language other than English? You can help translate WordPress into more than 100 languages! Release Candidate 1 marked the hard string freeze point of the 5.9 release schedule. Thanks to every locale that is already involved with translations.

Developers and those interested in more of the background to the features can find more in the Field Notes. More developer notes will be added as the release progresses to its final stage. You can also follow the 5.9 development cycle and timeline.

If you think you have found a bug, you can post the details to the Alpha/Beta area in the support forums.

 If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac, where you can also check the issue against a list of known bugs.

Props to: @psykro and @webcommsat, and @hellofromtonya, @audrasjb, @cbringmann and @marybaum for final review.

WordPress 5.9 RC 1

The first Release Candidate (RC1) for WordPress 5.9 is now available! 

Thank you to everyone who has contributed to reach this important milestone in the community’s progress towards a WordPress 5.9 release.

“Release Candidate” means the new version of the software is ready for release. It helps the community check that nothing is missed, given the thousands of plugins and themes and differences in how millions of people use the software.

WordPress 5.9 is slated for release on January 25, 2022. This is just three weeks to go  – and there’s still time to help!

Testing the release

You can test the WordPress 5.9 release candidate in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the beta version here (zip).

Option 3: When using WP-CLI to upgrade from Beta 1, 2, 3 or 4 on a case-insensitive filesystem, please use the following command sequence:

Command One:

wp core update --version=5.9-RC1

Command Two:

wp core update --version=5.9-RC1 --force

Your help to test the RC1 is vital: the more testing that happens, the more stable the release, and the better the experience for users and developers—and the entire WordPress community.

Thank you to all of the contributors who tested the Beta releases and gave feedback. Testing for bugs is not just a critical part of polishing every release; it is also a great way to contribute to WordPress.

Help test WordPress 5.9 features – a guide to how you can take part.

What is in WordPress 5.9 release candidate?

This will be the first release of 2022 and continues the work towards 5.9 from last year. It features the latest advances of the block editor and is the first version of full site editing in Core.

WordPress 5.9 also brings more refinements to the developer experience. To keep up with the latest updates and discover more about how the community works to continually improve the software, please subscribe to the Make WordPress Core blog. In particular, the developer notes tag will keep you up to date on changes that might affect your products or how you use the software.

Plugin and Theme Developers

Please test your plugins and themes against WordPress 5.9 and update the Tested up to version  to 5.9 in your readme file. If you find compatibility problems, please post to the support forums, so volunteers and developers can help you figure them out before the final release.

The WordPress 5.9 Field Guide will be out very shortly. It will give you a deeper dive into the major changes.

How to Help

Do you speak a language that is not English? You can help translate WordPress into more than 100 languages! Release Candidate 1 marks the hard string freeze point of the 5.9 release schedule. Thanks to every locale that is already involved with translations.

If you think you have found a bug, you can post to the Alpha/Beta area in the support forums.  If you are comfortable writing a reproducible bug report, you can file one on WordPress Trac, where you can also check the issue against a list of known bugs.

Props to @webcommsat for the post and to @marybaum @hellofromtonya @audrasjb @davidbaumwald @estelaris @cbringmann for final review.

WordPress 5.9 Beta 4

WordPress 5.9 Beta 4 is now available for testing!

This software version is still under development. Please do not run this software on a production site; install it on a test site, where you can try out the newest features and get a feel for how they will work on your site.

You can test the WordPress 5.9 Beta 4 in three ways:

Option 1: Install and activate the WordPress Beta Tester plugin (select the “Bleeding edge” channel and “Beta/RC Only” stream).

Option 2: Direct download the beta version here (zip).

Option 3: When using WP-CLI to upgrade from Beta 1, 2, or 3 to Beta 4 on a case-insensitive filesystem, please use the following command sequence:

Command One:

wp core update --version=5.9-beta4

Command Two:

wp core update --version=5.9-beta4 --force

The current target for the final release of 5.9 is January 25, 2022, which is only five weeks away. Your help testing this beta is vital: the more testing that happens, the more stable the release, and the better the experience for users and developers—and the entire WordPress community.

Some Highlights

Since Beta 3, 20 bugs have been fixed. Here are a few of the changes you will find in Beta 4:

  • Bundled Theme: Fixed duplicate CSS rules in Twenty Twenty-One theme (#53605).
  • Customizer: It’s possible to switch to a block theme from within Customizer (#54549).
  • Themes: Provide guidance to users seeking to preview block themes on WordPress versions below 5.9 (#54575).
  • REST API: The get_theme_item method should respect fields param (#54595).
  • Editor: Block Patterns: “Featured” category & patterns missing from inserter (#54623).
  • Login and registration: Add a filter to allow to disable the Login screen language dropdown – (#54675).

How You Can Help

Do some testing!

Testing for bugs is vital for polishing the release in the beta stage and a great way to contribute. 

Please post to the Alpha/Beta area in the support forums if you find a bug. If you’re comfortable writing a reproducible bug report, file one on WordPress Trac, where you can also find a list of known bugs.

Got questions? Here are some answers

In the coming weeks, follow the Make WordPress Core blog for 5.9-related developer notes that will cover these items in detail.

So far, contributors have fixed 326 tickets and 108 new features and enhancements in WordPress 5.9. More bug fixes are on the way with your help through testing.

Props to @cbringmann, @psykro@hellofromtonya@marybaum@webcommsat, @audrasjb, @cbringmann, @costdev and @meher for contributions to this post.