[wp-trac] [WordPress Trac] #53333: Better handling for forced plugin autoupdates

[WordPress Trac]

#53333: Better handling for forced plugin autoupdates
-----------------------------+------------------------------
 Reporter:  dd32             |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-patch early  |     Focuses:
-----------------------------+------------------------------
Changes (by dd32):

 * keywords:  has-patch => has-patch early


Comment:

 > An attached PR explores this idea, although will be pending
 implementation on WordPress.org prior to it being testable. I've got a
 draft 1.2 endpoint that works like this, and will follow up with that next
 week pending feedback from others.

 Just noting that the `/plugins/update-check/1.2/` API is now available for
 testing, if anyone wants to look into it.. but without an active auto-
 update in progress, it's hard to test it. I'll see if I can get a plugin
 setup that will have an auto-update available for testing.

 As far as I can tell, although I've not tested it, this should work with
 any plugins which define a 3rd-party plugin update mechanism, as long as
 they intercept/alter the `plugins/update-check/*/*` requests or use the
 other core filters added for the `Update URI` headers.

 This change should be made early in a release cycle, and not rushed.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/53333#comment:2>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform