Back to Community
Home / Community / Core → Developing with wordpress

Resolving the 'Plugin Not Tested with Latest WordPress' Warning

39 threads Sep 16, 2025 Core → Developing with wordpress

Content

If you're a plugin developer, you've likely encountered a frustrating warning on your WordPress.org plugin page: "This plugin hasn’t been tested with the latest 3 major releases of WordPress." This message can deter users from installing your plugin, even if it's fully compatible. Based on community reports and solutions, this guide will explain why this happens and how to fix it.

Why This Warning Appears

WordPress.org automatically parses your plugin's readme.txt file to display information like the "Tested up to" version. The warning is triggered when the system cannot find this file or cannot correctly read the "Tested up to" header. This is often not a problem with your version number, but with the file itself being missing or inaccessible to the parsing system.

How to Fix It

The most common solution, as confirmed by user reports, is to verify the presence and location of your readme.txt file.

  1. Check Your Upload/Deployment Process: Ensure your readme.txt file is in the root directory of your plugin's SVN trunk. A missing file is the primary cause of this warning.
  2. Validate Your Readme Syntax: Use the WordPress Readme Validator to check for any formatting errors that might prevent parsing.
  3. Confirm the Stable Tag: Ensure the "Stable tag" in your readme.txt points to a valid SVN tag that exists (e.g., Stable tag: 1.0.0). The system may also throw warnings if it's set to /trunk/.
  4. Be Patient: After committing a corrected readme.txt to SVN, note that it can take some time for the WordPress.org system to refresh its data. The change is not always instantaneous.

Example of a Correct Readme Header

=== My Awesome Plugin ===
...
Requires at least: 6.0
Tested up to: 6.7.2
Stable tag: 1.5.0
Requires PHP: 7.4
...

By meticulously checking your deployment process and the readme.txt file, you can resolve this warning and assure users that your plugin is compatible with the latest versions of WordPress.

Related Support Threads Support