/core resource #1500

I'd like to propose a /core resource, which gives some information about the WordPress install, and a way to manage core and language pack updates.

Here's a brief outline of the endpoints:

GET /core

• No parameters
• Return
  • WordPress version
  • Default language

GET /core/updates

While the W.org API returns much more info about available downloads, I don't think it's necessary to include that here, as there's nothing the UA could do with it. If they did need that information for some unknown reason, it's easy enough for them to call the W.org API directly.

• No parameters
• Return
  • List of core updates available
    • Update version
    • major/minor flag
  • List of language pack updates available
    • language
    • core/plugin/theme flag

PUT /core/updates

• Parameters
  • List of updates to install
    • type: core, language pack, DB
    • version (core only)
    • language (language pack only)
    • core/theme/plugin flag (language pack only)
• Return
  • List of updates installed
    • For core updates, whether there needs to be a DB update
  • Errors for failed updates

As minor core updates and language packs are installed automatically, it's likely that the update will have occurred by the time /core/updates is called. The UA should be prepared to handle this.

This is a starting point for the discussion on this resource.

• Are there other endpoints we'll need?
• Are these the correct verbs? Do we need more information returned by these endpoints?
• Given the likelihood of these endpoints causing maintenance mode, do we need to be reminding UAs how to handle that situation?