Closed (fixed)
Project:
Drupal core
Version:
10.2.x-dev
Component:
composer
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
28 Nov 2023 at 16:02 UTC
Updated:
14 Dec 2023 at 18:19 UTC
Jump to comment: Most recent
Drupal 10.2.0-rc1 is due this week, a number of dependencies have minor and patch level release bumps that we should try to incorporate in the release.
$ composer outdated
$ composer update --with=phpunit/phpunit:^9
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:
Comments
Comment #3
longwaveComment #5
longwaveLooks like we found a PHPStan bug, or at least an incorrect error message - opened https://github.com/phpstan/phpstan/issues/10219
Root cause appears to be the complex return type of
_file_save_upload_from_form(). Discussed with @mglaman and we can likely work around it by adding anis_array()check.Comment #6
longwaveThis was already reported at https://github.com/phpstan/phpstan/issues/10189
Comment #7
mglamanhttps://github.com/phpstan/phpstan-src/pull/2794 has been merged and fixes the PHPStan error pending next release
Comment #8
longwaveAdded an
is_array()check. Alternatively we could perhaps add a @var comment to force PHPStan to understand it's an array? Not sure which is better.Or, we could just wait for the next release, and not bump PHPStan for now?
Comment #9
mglamanI say we wait for the PHPStan release. The array checks will be covered when PHPStan levels bump – that a non-array may be passed to array_filter. I think it's best to fix types when they arise once PHPStan begins to uncover them with increased levels.
Comment #16
spokjeEDIT: I've seem to not submit my previous comment, which stated I was #TeamNotBumpPHPStan and an added
conflictin the rootcomposer.jsoncould help us out.Original comment below.
Sorry for the noise, did some pushes to a wrong branch.
Anyway: I forgot that with the conflict in place we can still do a
composer update --with=phpunit/phpunit:^9and be done with it. It bumpsphpstan/phpstanto the latest version that has no conflict (1.10.44).With this MR !5580 we now can either wait until the next PHPStan release, which will have the fix, or, if sooner, release Drupal 10.2.0-rc1 and afterwards remove the conflict and bump the version number of
phpstan/phpstanin the rootcomposer.json.Comment #17
spokje--removed outdated
composer-lock-diff--Comment #18
spokjeUpdated MR!5580 with freshly released SF6.4.0 https://github.com/symfony/symfony/releases/tag/v6.4.0
Comment #19
longwave@Spokje wow that was fast - 10 minutes after release of 6.4.0!
Comment #20
andypostAdded update will help with SF7 support https://github.com/asm89/stack-cors/compare/v2.1.1...v2.2.0
Comment #21
andypostMaybe the same time to bump
mglaman/phpstan-drupalto 1.2.4 inrequire-devas it's pinned to this version already?Comment #22
longwave@andypost we usually only bump requirements if we needed to change something and the old version would fail in some way
Comment #24
spokjehttps://github.com/colinodell/psr-testlogger/releases/tag/v1.3.0
For MR!5580:
Comment #25
longwaveLooks great, thank you. Let's land this for 10.2.0-rc1.
Comment #28
alexpottI don't think we should have added conflicts here. I think they are largely pointless for upstream dependencies because they are not retroactive so can result in composer solving to an odd set of dependencies for a project. But given this is only going to be the case for a short while ...
Committed this to 11.x and 10.2.x, thanks!
Comment #30
mondrakeAre these deprecation ignores still 'temporary' at this point?
https://git.drupalcode.org/project/drupal/-/blob/11.x/core/.deprecation-...
Is there a followup to remove them or to make them more permanent if they have to stay?
Comment #31
longwave#3397522: Fork Symfony's ContainerAwareTrait and ContainerAwareInterface into core is trying to figure out next steps here, whether we need to fork
ContainerAware*or remove uses of it if we can.Comment #32
mondrakeHow about linking that issue in the .deprecation-ignore.txt file?