[wp-meta] [Making WordPress.org] #4468: Plugin Update Check API returns tested field without patch version
Making WordPress.org
noreply at wordpress.org
Wed May 22 22:02:16 UTC 2019
#4468: Plugin Update Check API returns tested field without patch version
------------------------------+-----------------------
Reporter: abrain | Owner: dd32
Type: defect | Status: accepted
Priority: normal | Milestone:
Component: Plugin Directory | Resolution:
Keywords: |
------------------------------+-----------------------
Changes (by dd32):
* owner: (none) => dd32
* status: new => accepted
* component: API => Plugin Directory
Comment:
This is caused by a few different things:
- Every hour the `tested` fields get updated if a new version becomes
available. This needs to happen a little bit more often than hourly I
think (or triggered by seeing `$wp_version` change)
- Every hour (and following a commit) the plugin data gets sync'd over to
the source-data of the Update API, which attempts to clear the caches for
the API endpoints. Unfortunately it only checks the `last_updated` field
and the automatic increase of the `tested` field doesn't trigger that.
I think the job that bumps the tested versions also needs to trigger the
API tasks, which I'll take a look into
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/4468#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list