Closed (fixed)
Project:
Drupal core
Version:
10.0.x-dev
Component:
base system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
20 Dec 2021 at 23:26 UTC
Updated:
31 Jan 2022 at 15:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
alexpottComment #3
alexpottFixing the patch
Comment #5
longwaveMaybe leave
asm89/stack-corsfor #3128982: Upgrade asm89/stack-cors to ^2.0 to fix cacheability andguzzlehttp/psr7for #3220220: Update guzzlehttp/psr7 to 2.1.0?Are there any breaking changes in
composer/installers2?I think major version bumps of anything require release manager signoff? In which case maybe only do the minor bumps here and leave majors to individual issues?
Comment #6
longwaveWe should also consider adding
replacelines for the PHP 7.4 and 8.0 polyfills as we no longer need them.edit: and local testing suggests we can remove
paragonie/random_compatandsymfony/polyfill-php70as nothing depends on those any more anyway - maybe let's spin off a separate issue for thisComment #7
alexpottWe don't use the API of composer/installers - I'm not sure we can even consider it having one. It still supports Drupal. I think the major change we the removal of support for lots of things that no longer need it. Would be interesting to see what Joomla has done... see https://github.com/composer/installers/blob/main/CHANGELOG.md
Comment #8
spokjeComment #9
andypostUpgrade of #3128982: Upgrade asm89/stack-cors to ^2.0 to fix cacheability gonna be tricky as new 2.1.0 release supports only SF6 but previous releases fails ATM with
Comment #10
alexpottUpdating all the things now the major updates have been done...
Yes the psr/cache library is changing major version here but imo that's okay this is not a major library for us.
Comment #11
alexpottChasing the updates...
Comment #12
longwaveLooks good to me, might as well get this in now before the next round :)
Comment #13
alexpottTrying to re-roll this issue now that SF5 has landed but this happens:
Which is really odd.
This will be fixed once https://github.com/symfony/service-contracts/commit/034c73d5dd4c05c71a27... lands. So I think we should go to a dev release of the service-contracts.
Comment #14
alexpottComment #15
alexpottOh damn - the dev package will not be allowed in an alpha...
Comment #16
alexpottOh changed minimum stablity to alpha and reran... and back to dev and updated lock hash.
Comment #17
alexpottLet's remove the change to core/composer.json - it's pointless - it only fixes running composer update... but until https://github.com/symfony/service-contracts/commit/034c73d5dd4c05c71a27... is released we're going to need to be careful while doing that anyway.
Comment #18
longwaveHmm, this will block our Symfony 6 upgrade.
Otherwise this looks fine and there will surely be many more rounds of upgrades on the way to Drupal 10.
@alexpott do you want to open a companion issue for Drupal 9.4, as we should bump deps there where we can as well?
Comment #19
gábor hojtsyMaking titlte more specific.
Comment #22
catchCommitted 80a83b4 and pushed to 10.0.x. Thanks!