Closed (fixed)
Project:
Drupal core
Version:
11.x-dev
Component:
composer
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
14 May 2026 at 23:25 UTC
Updated:
30 May 2026 at 17:00 UTC
Jump to comment: Most recent
Comments
Comment #3
andypostUpdated previous CR https://www.drupal.org/node/3464803
Comment #4
claudiu.cristeaComment #5
dwwIs it worth changing anything in core to use at least one of the new functions as part of this issue? So we see that tests still pass, and so we see what kinds of improvements the new functions would unlock? Otherwise, seems this is adding an unused dependency, and the release managers tend not to like doing that. 😅
Comment #6
mstrelan commentedWe've had some of these polyfills go in on their own in the past, and they have proven useful particular for back ports, e.g. an MR targeting 11.x could use PHP 8.3 functions and backport easily to 10.x. It also makes it easier for contrib to use new language features. IMHO we should get this in without finding usages.
Comment #7
dwwMakes sense to me. I’m all for it, was only trying to channel my inner release manager. 😂 change is simple enough and looks good. Bot is happy (as expected). Let’s see what a committer thinks.
Comment #8
alexpottComment #9
alexpottCommitted and pushed 0d464ba79b0 to main. Thanks!
Comment #13
andypostcreated 11.x MR
Comment #14
alexpottComment #15
alexpottCommitted c78fd35 and pushed to 11.x. Thanks!