[wp-meta] [Making WordPress.org] #5412: Add offers for 'release-candidate' and 'beta' to Core API version check

Making WordPress.org noreply at wordpress.org
Wed Sep 2 22:31:50 UTC 2020


#5412: Add offers for 'release-candidate' and 'beta' to Core API version check
-------------------------+--------------------
 Reporter:  afragen      |      Owner:  (none)
     Type:  enhancement  |     Status:  new
 Priority:  normal       |  Milestone:
Component:  API          |   Keywords:
-------------------------+--------------------
 Core API version check at https://api.wordpress.org/core/version-
 check/1.7/?version=5.7-wp-beta-tester displays offers for `development`,
 `latest`, and `autoupdate`.

 In a recent thread in #core-committers @matt asked ''if there was an easy
 way to flag auto-updates for release candidates and stable, but not beta
 or alpha.''
 https://wordpress.slack.com/archives/C18723MQ8/p1599065974000500

 If there were Core API offers for `release-candidate` and `beta`, in
 addition to the currently used `development`, I believe it would be
 possible to more easily modify the WordPress Beta Tester plugin to select
 these streams. Currently the Beta Tester plugin does a lot of manipulation
 to set updating to a beta or RC release. Most of this work by @pbiron.

 For `beta` the download should display the current or next (potential)
 beta release. For `RC` the download should display the current or next
 (potential) RC release.

 Currently the Beta Tester plugin determines which is the next available
 beta/RC by checking for a 200 response to the standardized download links.

 I think adapting the API and the Beta Tester plugin will likely yield the
 simplest implementation.

 Obviously the API offer would change depending on the query passed.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5412>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list