Problem/Motivation
We should update our dependencies before Drupal 10.2.0.
I see two possibilities:
- We can get this one in now, and do another update round just before the first 10.2.0(-beta?) release
- We wait until just before the first 10.2.0(-beta?) release, update the updates and get this one in.
I really don't mind either option, this issue was opened now to make sure we don't hit any unexpected surprises (which we shouldn't due to our daily "updated deps" QA run)
Steps to reproduce
$ composer outdated
Proposed resolution
$ composer update --with=phpunit/phpunit:^9
Remaining tasks
#3358319: Update to PHPUnit 9.6.13 and replace deprecated assertObject[Not]HasAttribute()
User interface changes
API changes
Data model changes
Release notes snippet
Issue fork drupal-3393151
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3393151-
compare
- 3393151-update-composer-dependencies
changes, plain diff MR !4985
Comments
Comment #2
spokjeComment #3
spokjeComment #4
quietone commentedThanks for opening this issue.
Comment #6
spokje@quietone: Ah, should have checked, of course you had already admin-ed the BLEEP out of meta-s.
Thanks!
Comment #7
spokjeSo, minor surprise detected.
Seems like the "updated deps" QA runs uses
composer update --with-all-dependencies --with phpunit/phpunit:$(composer show -i |grep phpunit\/phpunit |awk '{print $2}') --working-dir /var/www/htmlwhich will keepphpunit/phpunitat exactly the same version.What we're doing (and have been doing) in update issues like these is
composer update --with-all-dependencies --with phpunit/phpunit:$(composer show -i |grep phpunit\/phpunit |awk '{ split($2, arr, "."); print arr[1]; }') --working-dir /var/www/htmlwhich keepsphpunit/phpunitat the same _major_ version.Comment #8
spokjeSo it looks like PHPUnit backported the previously 10.1+ methods
assertObject[Not]HasPropertyto 9.6.I'm unsure about 2 things now:
1) I think we should repurpose #3358319: Update to PHPUnit 9.6.13 and replace deprecated assertObject[Not]HasAttribute() to update PHPUnit to the latest 9.6 version and use the above method to replace the deprecated ones. Doing this in a separate issue means we can backport this down to core 10.1.x.
2) We would have caught this a lot earlier if we used #8 in our daily "updated deps" run. Not sure if it's worth opening an issue for that since GitLab has priority. On the other hand: Can't open an issue for GitLab since that doesn't have a "updated deps" run.
Comment #9
spokjeComment #10
smustgrave commentedI like that idea @Spokje of moving the phpunit out to a separate issue. Feel there could be some back n forth for that and no reason to delay the others. Could you revert the phpunit update please.
Comment #11
spokjePostponing this until #3358319: Update to PHPUnit 9.6.13 and replace deprecated assertObject[Not]HasAttribute() lands.
Comment #13
quietone commentedAdding postponed item to remaining tasks per details to include in the 'Remaining tasks'.
Comment #14
quietone commentedComment #16
quietone commentedComment #17
spokjeMore compact change list now.
Got the same results as the MR locally with a
$ composer update --with-all-dependencies --with phpunit/phpunit:^9.Would RTBC, but messed with this one myself.
Comment #18
smustgrave commentedYay for updates!
Comment #19
alexpottCommitted and pushed e24ba3f4484 to 11.x and 441439c6f6a to 10.2.x. Thanks!
Comment #22
mondrakemglaman/phpstan-drupal just released 1.2.1.