WordPress 6.7 is scheduled for release on November 12, 2024. Are your plugins ready?

[musamamasood]

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.
• HTML API: Major improvements, including full HTML support, a new full-parser mode for parsing a full HTML document, and more. https://make.wordpress.org/core/2024/10/17/updates-to-the-html-api-in-6-7/
• Internationalization: A warning will now be thrown if translations are loaded too early (before 'after_setup_theme' or 'init'). https://make.wordpress.org/core/2024/10/21/i18n-improvements-6-7/
• New block type registration APIs: Improve the performance of registering block types, especially for plugins that register multiple block types. https://make.wordpress.org/core/2024/10/17/new-block-type-registration-apis-to-improve-performance-in-wordpress-6-7/
• New plugin template registration API: Plugins can now directly register and unregister block templates. https://make.wordpress.org/core/2024/10/20/new-plugin-template-registration-api-in-wordpress-6-7/

For a more comprehensive overview of all the upcoming changes, check out the WordPress 6.7 Field Guide at https://make.wordpress.org/core/2024/10/23/wordpress-6-7-field-guide/, which will continue to be updated leading up to the release day (November 12).

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/

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.7. Users can feel more confident that they will not encounter any problems with your plugin when they update to the latest WordPress version.

Tip: You can make use of the Plugin Check plugin to help you spot and fix some common issues in plugins. Learn more here: https://make.wordpress.org/plugins/2024/09/17/introducing-plugin-check-pcp/.

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:

• https://wordpress.org/plugins/wp-front-end-profile/ (tested up to 6.7)

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.

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.7 as much as we do.