Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
We should ship Drupal 9.0 with the latest versions of our dependencies.
Proposed resolution
Update all dependencies.
Remaining tasks
Patch, test, fix any fallout, commit.
PHPUnit 8.5.3 has a seemingly relevant release note: "expectExceptionMessageRegExp() has been removed in PHPUnit 9 without a deprecation warning being given in PHPUnit 8"
User interface changes
None
API changes
None
Data model changes
None
Release notes snippet
Drupal 9 ships with the latest versions of all of its dependencies.
Comment | File | Size | Author |
---|---|---|---|
#36 | 3127674-9.1.x-36.patch | 26.79 KB | jungle |
#36 | 3127674-9.0.x-36.patch | 26.79 KB | jungle |
Comments
Comment #2
longwaveComment #4
catchBumping to critical.
Comment #5
longwaveUpdated the assertion method in three tests, also the composer lock hash calculation method now has to take the options into account.
Comment #6
mondrake#5 IMHO it would be better to silence the warnings by adding the relevant string in the PHPUnit8Warnings trait, and then file a follow-up to do the conversions as part of #3110543: [meta] Support PHPUnit 9 in Drupal 9
Comment #7
jungleDoubt there are unexpected changes to composer.lock file in #2. Let CI prove it.
In the patch
composer.lock
is from my localcomposer.lock.longwave
is from #2Expected outputs:
"diff composer.lock composer.lock.jungle"
: empty"diff composer.lock composer.lock.longwave"
: non emptyComment #8
jungleIMO, the output from CI proved there are unexpected changes to composer.lock, see https://dispatcher.drupalci.org/job/drupal_patches/42057/console
Comment #9
jungleComment #10
longwaveI used Composer 1.10.5 to do the update, that probably explains the differences. We specify 1.10.5 in the lock file as well so I think updates should be done with the same version?
Comment #11
jungleAll differences point to funding/tidelift. Not a user of it/No idea what is it. Is it a custom composer repository you are using?
Comment #12
jungleOn my local it's 1.9.0, inside the CI/Container, it's
Composer version 1.9.3 2020-02-04 12:58:49
Comment #13
catchThe latest version of composer adds funding information to composer.lock, not sure when it was introduced.
We might want a separate issue to update composer.lock for the funding changes, so that it doesn't affect other patches in the queue?
Comment #14
jungleComposer 1.10: composer fund, https://blog.packagist.com/composer-fund/
Make sense now, it's a new feature introduced at Composer 1.10.
Comment #15
jungleComment from @greg.1.anderson on slack
Comment #16
jungleA separate issue created to add funding info in composer.lock (3127918)
Comment #17
longwaveDowngraded to Composer 1.9 and I get the same results as #9. We also no longer need the composer lock hash calculation changes, and I have also implemented the suggestion in #6 as I now agree that fixing the tests here is technically out of scope.
Comment #18
jungle3121885 updated coder module targeting 8.9.x, if it gets ported to 9.0.x, then here needs a reroll probably.
Comment #20
jungleFix warning
Comment #21
longwaveWhy isn't the warning in #20 caught by the PHPUnit8Warnings trait?
edit: I see, it's a Component and the test directly extends TestCase, and as the components are supposed to be standalone we can't include PHPUnit8Warnings here.
Comment #22
mondrake#21 because that's a test for a component, that's likely extending from PHPUnit's
TestCase
directly, so the trait is not used... IMHO it's betteruse
the trait for now, so that we can orderly remove the deprecated call lateredit - xposted
Comment #23
mondrakeI suppose this needs a reroll now.
Comment #24
piyuesh23 CreditAttribution: piyuesh23 at QED42 commentedComment #25
imalabyaComment #26
imalabyaRerolled the patch.
Comment #27
imalabyaComment #28
mondrakeThis was removed in HEAD and is being added back, should be removed.
Comment #29
imalabyaUpdated the patch.
Comment #30
mondrakeLGTM. Adds a PHPUnit8 deprecation warning silencer that was missing up to PHPUnit 8.5.2, that we are going to need to work on PHPUnit9 support.
Comment #31
mondrakeComment #32
mondrakeUh-oh. Looks like we need a separate patch for 9.1.x
Comment #33
jungleA patch for 9.1.x, the patch for 9.0.x is in #29
Comment #34
jungleRe-roll again the patch for 9.1.x due to a new commit ~40 mins ago from the upstream.
Comment #35
jungleComment #36
jungleComment #37
jungleChanges of the 9.0.x patch in #36
Changes of the 9.1.x patch in #36
Comment #38
mondrakeThank you for the rerolls.
Comment #41
catchCommitted/pushed to 9.1.x and also to 9.0.x, thanks!
Comment #43
xjmNeeds a more helpful release note.
Comment #44
xjmComment #45
xjmI merged the release notes for this into #3133442: Update dependencies for Drupal 9.0.