Add "Requires PHP" information to Update API endpoint

[schlessera]

As @SergeyBiryukov has pointed out in ​https://core.trac.wordpress.org/ticket/43987#comment:9, the update information for plugins does not contain the PHP requirements that were introduced with #2952.

To avoid multiple requests, it would be useful to add this requires_php key to the API as well, as that plays a fundamental part in deciding whether an update is available or not.

[afragen]

So just to start the conversation…

If the update transient package for each plugin contained the data for requires and requires_php then that data could be used in combination with new core code to unset specific $transient->response entries that don’t meet requirements.

Additionally, we could add a force_update, or similar element, to allow for updates to older versions requiring security updates.

Any thoughts? @dd32

[dd32]

If the update transient package for each plugin contained the data for requires and requires_php then that data could be used in combination with new core code to unset specific $transient->response entries that don’t meet requirements.

The requires_php field has been present since 2018-04-10, and has contained the correct non-null value since 2018-05-08.

Is there anything missing from the WordPress.org side there?

[afragen]

Thanks for pointing this out @dd32, I missed it.

[joyously]

Is it just plugins? Or for themes also?

(I know themes don't have the same structure as in readme.txt, etc. but wondered if the API was able to handle themes if we change themes to use a readme.txt like plugins.)

[dd32]

This is just for plugins. Themes do not yet support readme.txts.

The Themes API can/will be extended when readme support is added to it, but it won't just be "magically supported".

[dd32]

I'm marking this as fixed as the data is there for plugins (as requested).