[wp-trac] [WordPress Trac] #61619: Display compatibility metadata for Dependent plugins
WordPress Trac
noreply at wordpress.org
Wed Jul 10 14:39:28 UTC 2024
#61619: Display compatibility metadata for Dependent plugins
-------------------------+------------------------------
Reporter: beccawitz | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Plugins | Version:
Severity: normal | Resolution:
Keywords: 2nd-opinion | Focuses:
-------------------------+------------------------------
Changes (by costdev):
* keywords: => 2nd-opinion
Comment:
Hi @beccawitz, thanks for opening this ticket!
Some history for others: **Maximum** version requirements were ruled out
at this time due to security best practices of ensuring users can update
dependency plugins without being restricted by a dependent plugin.
> Required minimum [Dependency Plugin] version: x.x.x (indicating the
minimum version of the Dependency plugin that should be used.
If this was to be implemented, I would also want to see a restriction on
the installation and activation of a dependent plugin if an installed
dependency is not at the correct minimum version, as is done with
PHP/WordPress minimum version requirements.
> Tested up to [Dependency Plugin] version: x.x.x (indicating the latest
version of the Dependency plugin that the Dependent plugin has been tested
with)
This would need some technical design consideration as to how to write,
parse, and detect the "[Dependency Plugin]", taking into account that
plugin names can be changed and are therefore unreliable. While
WooCommerce, for example, has a "WC tested up to" header, in that case
WooCommerce is committing to that format as the dependency, which won't be
the same when the dependency isn't aware that it's a dependency and that
decision is made by the dependent plugin author.
> Additionally, it would be beneficial to have an API that allows
Dependency plugins to gather data about the minimum versions and latest
tested versions being used by Dependent plugins.
I think this would likely need to be a separate ticket as it would need
its own discussion and consideration.
-----
I'll add the `2nd-opinion` keyword to attract additional opinions to this
discussion.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/61619#comment:1>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list