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

[Making WordPress.org]

#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          |  Resolution:
 Keywords:               |
-------------------------+---------------------

Comment (by dd32):

 @afragen I've deployed my changes.

 If I'm not around and this broke something, revert r16453-dotorg (for
 those who have access :) )

 https://github.com/WordPress/wordpress-develop/pull/520 is an example of a
 core change we could make to allow `WP_AUTO_UPDATE_CORE` to be set to `rc`
 or `beta`.

 As I mentioned, I've included a parameter to simulate releases (only
 Beta/RC releases!)

  - Running WP 5.5.1, want RC updates, and 5.6-beta1 has been released.
 should return `latest`: https://api.wordpress.org/core/version-
 check/1.7/?version=5.5.1&channel=rc&pretend_releases[]=5.6-beta1
  - Running WP 5.5.1, want beta/RC updates, and 5.6-beta1 has been
 released. should return `development` and beta1:
 https://api.wordpress.org/core/version-
 check/1.7/?version=5.5.1&channel=beta&pretend_releases[]=5.6-beta1
  - Running WP 5.5.1, want beta/RC updates, and 5.6-beta1/RC2 have been
 released. should return `development` & RC2:
 https://api.wordpress.org/core/version-
 check/1.7/?version=5.5.1&channel=beta&pretend_releases[]=5.6-beta1&pretend_releases[]=5.6-RC2

 You can look at the `X-Update-Channel` to see what it's determined a
 request to be, you should be able to look at the existing Beta Tester
 responses to see that too.

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