You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After you've tested your plugins and know they're compatible, take a moment to change the readme "Tested up to" value to 6.5. Users can feel more confident that they will not encounter any problems with your plugin when they update to the latest WordPress version.
If your plugins are compatible with their current version, you do not need to release a new version. All you need to do is update the "Tested up to" value to 6.5 in the readme.txt file under your stable tag directory.
Note that if a plugin is not marked as compatible with one of the three latest major WordPress releases, a warning will be displayed on its WordPress.org plugin page indicating that the plugin may no longer be maintained or supported. That notice will appear even if the plugin is still perfectly compatible with the current version. The trigger for the notice is strictly the "Tested up to" value in the readme.
WordPress 6.5 is scheduled for release on March 26, 2024. Are your plugins ready?
Highlights of the release include:
https://make.wordpress.org/core/2024/03/04/interactivity-api-dev-note/
https://make.wordpress.org/core/2024/03/14/new-feature-font-library/
https://make.wordpress.org/core/2024/03/06/new-feature-the-block-bindings-api/
https://make.wordpress.org/core/2024/03/05/introducing-plugin-dependencies-in-wordpress-6-5/
https://make.wordpress.org/core/2024/03/04/script-modules-in-6-5/
https://make.wordpress.org/core/2024/02/27/i18n-improvements-6-5-performant-translations/
https://make.wordpress.org/core/2024/02/23/wordpress-6-5-adds-avif-support/
https://make.wordpress.org/core/2024/03/04/updates-to-the-html-api-in-6-5/
Additional Updates / Breaking Changes:
For a more comprehensive overview of all the upcoming changes, check out the WordPress 6.5 Field Guide at https://make.wordpress.org/core/2024/03/15/wordpress-6-5-field-guide/, which will be updated leading up to the release day (March 26).
There have also been a few notable changes to the Plugin Directory recently:
https://developer.wordpress.org/plugins/wordpress-org/previews-and-blueprints/
https://meta.trac.wordpress.org/ticket/7477
How to test and update your plugins
You can learn about getting the release candidate version for all your testing in this guide: https://make.wordpress.org/core/handbook/testing/beta-testing/.
After you've tested your plugins and know they're compatible, take a moment to change the readme "Tested up to" value to 6.5. Users can feel more confident that they will not encounter any problems with your plugin when they update to the latest WordPress version.
Want to know more about a plugin's readme.txt file? Some great information lives here: https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/.
Here are the current "Tested up to" values for each of your plugins:
If your plugins are compatible with their current version, you do not need to release a new version. All you need to do is update the "Tested up to" value to 6.5 in the readme.txt file under your stable tag directory.
Note that if a plugin is not marked as compatible with one of the three latest major WordPress releases, a warning will be displayed on its WordPress.org plugin page indicating that the plugin may no longer be maintained or supported. That notice will appear even if the plugin is still perfectly compatible with the current version. The trigger for the notice is strictly the "Tested up to" value in the readme.
If you don't want to keep maintaining your plugin, you can close it down by following the instructions on the advanced tab on your plugin page: https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/#how-do-i-close-my-plugin.
For questions and support, you may also want to know about the new plugin support forums guidelines: https://make.wordpress.org/support/2023/10/new-support-guidelines/.
Thank you for all you do for the WordPress community, and we hope you will like 6.5 as much as we do.
— WordPress core contributors
The text was updated successfully, but these errors were encountered: