[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 johnbillion):

 I also agree about the maintenance burden. I had hoped that we wouldn't
 need to go this far but I started thinking about future proofing.

 Thinking about it further, we have [https://github.com/WordPress
 /wordpress-develop/pull/8138#issuecomment-2598170412 the same catch-22
 situation that I mentioned here] in that core can't make use of a new
 response parameter from the API until it's at least updated to a core
 version that supports it. 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.)

 Perhaps we should park this for now. Unfortunately there's not much we can
 do about the handful of sites that don't have `hash` installed that update
 to 6.8 -- they'll end up getting updated but going down with an error
 about the missing extension.

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