Strange "Tested up to" value

[Zodiac1978]

This plugin shows "6.8" as "Tested up to" value:
https://wordpress.org/plugins/apcu-manager/

But there is no "6.8" anywhere. It is 6.7 is trunk and the recent tag:
https://plugins.svn.wordpress.org/apcu-manager/trunk/readme.txt
https://plugins.svn.wordpress.org/apcu-manager/tags/4.1.0/readme.txt

And the for the "Git Updater" from Andy Fragen it is shown as "6.8.2", but the plugin only uses "6.8":
https://github.com/afragen/git-updater/blob/develop/readme.txt#L8

Any idea why the plugin is showing this wrong values?

[apermo]

I did some research on this and here's what I found:

How "Tested up to" is currently retrieved

The plugin uses plugins_api( 'plugin_information', ... ) (rt-plugin-report.php, line 349) to fetch plugin metadata from the wordpress.org API. The tested field from the API response is displayed directly — the plugin never reads the local readme.txt.

Case 1: apcu-manager showing "6.8" instead of "6.7"

The wordpress.org API itself returns a wrong value here. Both the trunk readme.txt and the latest tag readme.txt say 6.7, but the API reports 6.8. This is a wordpress.org-side issue — the API sometimes returns values that don't match what's actually in the readme.txt. Plugin Report just displays what the API returns.

Case 2: Git Updater showing "6.8.2" instead of "6.8"

Git Updater uses a custom Update URI pointing to GitHub. Because of that, Plugin Report correctly skips the plugins_api() call (line 348). However, Git Updater hooks into WordPress's plugins_api filter and injects its own metadata. The tested value it provides appears to be the running WordPress version (6.8.2) rather than the value from its own readme.txt (6.8).

Proposed fix

Since the wordpress.org API can be unreliable and non-wp.org plugins may inject wrong values (or no values at all), I've added a local readme.txt fallback: when repo_info->tested is not available, the plugin now parses the Tested up to header directly from the plugin's local readme.txt file.

This primarily helps non-wordpress.org plugins (custom Update URI) that previously showed "No data available" in the Tested column. For wordpress.org plugins, the API value is still used as the primary source since it reflects the latest published version (which may differ from the installed version).

Draft PR: apermo#1 — feel free to take it from there.

[Zodiac1978]

The wordpress.org API itself returns a wrong value here.

I am wondering why this happens. If wp.org is relying on SVN and there is a mismatch between SVN and readme.txt, we maybe should report this and show both instead of falling back to one side.