[wp-meta] [Making WordPress.org] #7641: Allow specifying `Tested up to` without changing the plugin

[Making WordPress.org]

#7641: Allow specifying `Tested up to` without changing the plugin
------------------------------+---------------------
 Reporter:  dd32              |       Owner:  (none)
     Type:  feature request   |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  2nd-opinion       |
------------------------------+---------------------

Comment (by dd32):

 > Are there any tools that analyze the readme declarations locally in a
 WordPress instance?

 There might be, but I don't think that's something we need worry about, we
 can't support every 3rd-party tooling.

 Any plugin that did something like "Hey, this plugin installed on your
 site (and probably working) isn't marked as compatible with your version
 of WordPress" seems like an extreme edge-case of usefulness? Given that
 the field isn't a "requirement" but rather a "suggestion" of what it's
 been tested with.

 > If there's no new version, then this change won't get replicated to
 installed copies of the plugin.

 FWIW This already happens. plugins often update the `Tested Up to` header
 without releasing a new version, so there's multiple variants of the same
 version of the plugin. Release confirmation prevents that though.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7641#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org