[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
Sat Sep 5 01:21:39 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          |  Resolution:
 Keywords:               |

Comment (by dd32):

 Replying to [comment:8 afragen]:
 > Just making sure that `channel=stable` is optional too.

 Yes! Optional parameters, but if not specified the "channel" is assumed
 based on the parameters (Which for most people, will be `stable` - or
 `development` if running on trunk). It's basically consolidating the
 various decisions the API currently makes into a singular label which can
 be set from the client instead of the API just guessing what the client

 For testing (and maybe even ongoing..) I'll include a response header that
 indicates what the channel it's using is, so you can verify it's behaving
 as expected (open-sourcing this specific API isn't straight forward, so
 I'm not attempting that right now, but wanted to make it more transparent)

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

More information about the wp-meta mailing list