Update "Tested up to" to avoid compatibility warning#220
Update "Tested up to" to avoid compatibility warning#220juanfra wants to merge 1 commit intoWordPress:developfrom
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #220 +/- ##
==========================================
Coverage 56.76% 56.76%
Complexity 505 505
==========================================
Files 32 32
Lines 2565 2565
==========================================
Hits 1456 1456
Misses 1109 1109
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Just saw there's a failing check for the "Tested up to" version number to only include major versions. Closing. |
|
According to the plugin readme guidelines, the I'm not seeing that warning message myself unless I'm running a site that is using a development version of WordPress (which then shows as 6.9.2) so I'm assuming you may be running the same. |
|
Thanks for checking! My bad, I didn’t realize until after opening the PR. |
What?
Updates the "Tested up to version" in the plugin header to the latest WordPress minor release so the plugin doesn’t show the compatibility warning in wp-admin. No functional changes.