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
WordPress 6.7 is scheduled for release on November 12, 2024. Are your plugins ready?
Highlights of the release include:
Block Editor: Merges Gutenberg v18.6-19.3, featuring continued iterations of the Interactivity API, Block Bindings API, Block Hooks, user interface APIs, and more.
Recent security changes for plugin authors on WordPress.org
The Plugin Directory has recently enforced enhanced security measures for WordPress.org plugin developer accounts. Two-factor authorization (2FA) is now mandated on all plugin owner and committer accounts. Also, an SVN password feature has been introduced to separate your commit access from your main WordPress.org account credentials. Learn more at: https://make.wordpress.org/plugins/2024/06/26/keeping-your-plugin-committer-accounts-secure/
After you've tested your plugins and know they're compatible, take a moment to change the readme "Tested up to" value to 6.7. 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.7 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.
The text was updated successfully, but these errors were encountered: