Add `core release` command(s) to fetch available releases through the .org API

[schlessera]

It would be useful to be able to easily query the available releases of WordPress core through the .org API and also get the download URLs for a given update.

A use case I'm currently working on that this would benefit is wp-cli/wp-cli-tests#51

[schlessera]

It doesn't seem to be possible to query for arbitrary patch version through the WordPress.org API. Am I missing something, like an extra query argument or a different endpoint?

[schlessera]

Also, the locale query for the API argument behave in an unexpected way as well. It does only produce a different result for the first (i.e. the "latest") release, all others seem to still point to en_US downloads...

[swissspidy]

Also, the locale query for the API argument behave in an unexpected way as well. It does only produce a different result for the first (i.e. the "latest") release, all others seem to still point to en_US downloads...

Maybe @ocean90 knows more here?

[schlessera]

Doesn't he always do?

[ocean90]

Can you tell me what endoints you are trying? What's the request looking like? To retrieve all available versions you could use https://api.wordpress.org/core/stable-check/1.0/.

[swissspidy]

The current code uses https://api.wordpress.org/core/version-check/1.7/ it seems.

[schlessera]

Yes, indeed, I'm using the version-check endpoint right now. If I have a specific version from stable-check endpoint, can I:

• retrieve detailed information for that specific version through version-check/some other endpoint with similar information?
• specify which locale to check for?

[schlessera]

The call to the stable-check is really slow and often times out. Is that endpoint not being cached?

[schlessera]

@ocean90 Do you know whether there might be a caching issue with stable-check ^^^?

[ocean90]

There's no caching for that endpoint.

[schlessera]

There's no caching for that endpoint.

Shouldn't that be changed, then? It seems slow and unreliable.