[wp-meta] [Making WordPress.org] #7900: Add `hash` as a required extension for 6.8

[Making WordPress.org]

#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):

 > We can't stop sites from updating to 6.8 based on required PHP
 extensions because no such check exists in 6.7. (This is what lead me to
 thinking about the update offer varying depending on the extensions query
 parameter.)

 The `update-core.php` file that's executed as part of the core upgrade is
 from the newer version. That is, the file included in `6.8` must be
 compatible with WP 3.0~6.7, as it'll be executed as part of the upgrade
 routine.

 That's why the `json` check linked above works, if a site attempted to
 update from 5.2 to 5.3 it would abort with a `Sorry, no JSON installed`
 and not take the site down.


 That's all to say, any API changes would only be able to affect future
 6.8+ required extensions, but we'd still have to have the checks in
 update-core.php to abort the upgrade for any older sites.

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