WordPress.org
Get WordPress

Making WordPress.org

Changes between Initial Version and Version 1 of Ticket #8403, comment 2


Ignore:
Timestamp:
08/19/2026 09:39:18 AM (8 weeks ago)
Author:
wprashed

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #8403, comment 2

    initial v1  
    1 +1 for this proposal. Having a machine-readable source for the bundled Gutenberg version would solve a real issue for hosts, plugins, and CI/CD pipelines that currently rely on maintaining fragile manual lookup tables.
    2 ### Implementation Considerations:
     1
     2**Implementation Considerations:
     3**
    341. **Backwards Compatibility:**
    45   Adding a `gutenberg_version` property to each item in the `offers` array of `https://api.wordpress.org/core/version-check/1.7/` is fully backwards-compatible, as WordPress core's `find_core_update()` ignores unrecognized offer fields.
    56   Example proposed structure:
    6    ```json
    7    {
     7
     8   
     9{{{
     10{
    811       "response": "upgrade",
    912       "download": "https://downloads.wordpress.org/release/wordpress-6.8.zip",
    … …  
    1417       "gutenberg_version": "20.1.0"
    1518   }
     19}}}
     20
    1621Data Storage & Pipeline: Rather than resolving Git SHAs dynamically on incoming requests, the release packaging workflow can resolve the corresponding Gutenberg version (from package.json at release build time) and persist it directly in the core release metadata table alongside the minimum PHP/MySQL versions.
    1722