[wp-meta] [Making WordPress.org] #7900: Add `hash` as a required extension for 6.8
Making WordPress.org
noreply at wordpress.org
Tue Feb 4 00:31:11 UTC 2025
#7900: Add `hash` as a required extension for 6.8
--------------------------+---------------------
Reporter: johnbillion | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone:
Component: API | Resolution:
Keywords: |
--------------------------+---------------------
Comment (by dd32):
The API has never enforced PHP extensions, that's left to `update-
core.php` in core which bails if the requirements aren't met.
https://core.trac.wordpress.org/browser/trunk/src/wp-admin/includes
/update-core.php?marks=1184-1195#L1171
The reasoning for this is
- Historically core did not send PHP extensions as part of the update
payload (and it's optional)
- The API doesn't (currently) return a `extensions_required` field that
core could be updated to check against (like it does `php_version`)
If core would like to update to add a `extensions_required` field to the
endpoint and have core flag this in the UI prior to attempting the
upgrade, that's something we can implement on WordPress.org.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/7900#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list