Tested with WordPress 6.1

[musamamasood]

WordPress 6.1 is scheduled to be released on November 1st. Are your plugins ready? After testing your plugins and ensuring compatibility, it only takes a few moments to change the readme "Tested up to" value to 6.1. This information provides peace of mind to users and helps encourage them to update to the latest version of WordPress. You can find more information about plugin readmes 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 5.9.5) For each compatible plugin, you do not need to release a new version — instead, you can update the "Tested up to" value to 6.1 in your readme.txt file. Remember that plugins that are not updated as tested with the latest 3 major releases of WordPress have a notice displayed on their WordPress.org plugin page noting that the plugin may no longer be maintained or supported. It's in everyone's best interest to continue testing plugins against WordPress versions and updating that value. If you would rather close your plugin because you no longer wish to maintain it, you may do so yourself via the advanced tab on your plugin page: https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/#how-do-i-close-my-plugin Looking to get more familiar with 6.1? Read this roundup post on the core development blog to learn more about the various changes coming to core with this major release: https://make.wordpress.org/core/2022/10/12/wordpress-6-1-field-guide/ There are a few areas that need specific focus as plugin-related changes are coming in 6.1; please review those that are most relevant to your plugin functionality:
  1. Content-only editing for blocks, patterns, and templates now allows limiting users to only change the nested content inside said blocks/patterns: https://make.wordpress.org/core/2022/10/11/content-locking-features-and-updates/
  2. The new "Style Engine" API provides a single, centralized agent responsible for generating and rendering consistent block supports styles on the client-side and server-side: https://make.wordpress.org/core/2022/10/10/block-styles-generation-style-engine/
  3. New server-side filters allow hooking into the theme.json data provided at the different data layers (default, blocks, theme, user): https://make.wordpress.org/core/2022/10/10/filters-for-theme-json-data/
  4. Query block can be further extended and customized through block variations: https://make.wordpress.org/core/2022/10/10/extending-the-query-loop-block/
  5. Block API changes in WordPress 6.1, including PHP templates for rendering blocks and the ability to use multiple scripts per block: https://make.wordpress.org/core/2022/10/12/block-api-changes-in-wordpress-6-1/
  6. Two new functions, wp_required_field_indicator() and wp_required_field_message(), help manage required fields in forms: https://make.wordpress.org/core/2022/10/10/functions-and-hooks-for-required-fields-in-wordpress-6-1/
  7. The @wordpress/core-data JavaScript package in 6.1 ships new React hooks that make accessing WordPress data easier than before: https://make.wordpress.org/core/2022/10/11/simplified-data-access-with-new-react-hooks-in-wordpress-6-1/
  8. New is_login() function for determining if a page is the login screen: https://make.wordpress.org/core/2022/09/11/new-is_login-function-for-determining-if-a-page-is-the-login-screen/

To ensure compatibility, here is how to download the latest Release Candidate for testing with your plugin: https://make.wordpress.org/core/handbook/testing/beta-testing/.