[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
Thu Sep 3 05:47:20 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):

 > if you let me know what query arg you’d like the plugin to send we could
 add it pretty simply. (Famous last words)

 Anything, that makes sense for core to maybe also use one day? I wasn't
 sure what it should be called so I didn't make a suggestion..

 > As far as the updates API only seeing files on the filesystem, couldn’t
 it create the beta or RC based on the existence of the actual release. Of
 course this would only show a download during the release party after it’s

 Yup, that's my thought - We'd be basing it on the existence of the file on
 disk, which is once it's packaged. We also store the `$wp_version` for
 each of the packages built (plus the nightlies).
 The original suggestion was `should display the current or next
 (potential) beta release` so I was thinking you meant "potential next
 beta, ie Beta1 released next Wednesday" rather than the Beta that would
 'officially' be released in a few minutes once the release party is over.

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

More information about the wp-meta mailing list