With the WordPress 6.7 RC out, perform the following:
[ ] E2e tests run only on the latest WP version, so Add needs: WP RC testlabel on the PR otherwise the tests will run on the latest released version of WordPress (6.6) instead of the 6.7 RC.
[ ] Open PR to bump WordPress "tested up to" to 6.7.
[ ] Bump WordPress minimum supported to 6.5.
[ ] Search codebase for conditionals on minimum version numbers no longer supported that could be removed.
[ ] Check to see if e2e tests pass, if so move the issue to UAT. If e2e tests fail, see if that's an issue with the test or compatibility with WP.
[ ] Check other files where the version needs to be bumped - For this the main thing to look for is the function version_compare and then see if we're checking WordPress versions there or something else (sometimes we check PHP versions for instance or Woo versions). Some plugins also define what WordPress version we support (sometimes as a minimum) in a constant (see Square as an example). There's not always consistent naming on those constants so really the easiest way to find these is to search the codebase for the version string. Search the last few releases to catch them all. Also, suggest looking at the last PR that bumped versions because to copy what was done for those.
[ ] Add compatibility fixes, where necessary
After bumping versions in a PR, we will ensure that e2e tests and overall plugin functionality continues to work as expected via regression testing following defined critical flows (if plugin functional compatibility changes were required).
Sample Changelog entry should then be:
Dev - Bump WordPress "tested up to" version 6.7.
Dev - Bump WordPress minimum supported version to 6.5.
With the WordPress 6.7 RC out, perform the following:
needs: WP RC testlabel on the PR otherwise the tests will run on the latest released version of WordPress (6.6) instead of the 6.7 RC.version_compareand then see if we're checking WordPress versions there or something else (sometimes we check PHP versions for instance or Woo versions). Some plugins also define what WordPress version we support (sometimes as a minimum) in a constant (see Square as an example). There's not always consistent naming on those constants so really the easiest way to find these is to search the codebase for the version string. Search the last few releases to catch them all. Also, suggest looking at the last PR that bumped versions because to copy what was done for those.After bumping versions in a PR, we will ensure that e2e tests and overall plugin functionality continues to work as expected via regression testing following defined critical flows (if plugin functional compatibility changes were required).
Sample Changelog entry should then be: