Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
Discovered whilst working on #3405696: Update composer dependencies for Drupal 10.2.0:
Looks like symfony/psr-http-message-bridge switched its semver 2.x schedule to the 6.x/7.x schedule of the main Symfony components.
Currently we have a constraint of ^2.1 on this dependency, which keeps it at 2.3.1 and doesn't allow an update to our (current) other SF ^6.4 components.
The code changes between 2.3.1 and 6.4.0 seem minimal.
Steps to reproduce
Proposed resolution
- Change the restriction on symfony/psr-http-message-bridge in core/composer.json from ^2.1 to allow both ^2.1 and ^6.4.
- $ composer update symfony/psr-http-message-bridge
Per @longwave in #5:
I think we should allow either version in composer.json for backward compatibility, but lock to the newer one as we are upgrading everything else to Symfony 6.4.
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
The constraint for the dependency on symfony/psr-http-message-bridge now allows both ^2.1 as before and ^6.4 for backward compatibility. In the composer.lock the constraint ^6.4 is used, since all other Symfony components are upgraded to that version.
Issue fork drupal-3405704
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:
changes
Comments
Comment #3
spokjeWould love to have this in 10.2.0, but since it's technically a major version bump and thus not allowed I need some guidance here.
Comment #4
spokjeComment #5
longwaveI think we should allow either version in composer.json for backward compatibility, but lock to the newer one as we are upgrading everything else to Symfony 6.4. That way, core-recommended users get bumped to the latest version but people can fall back to the older one if something else has a hard requirement on it.
Comment #6
spokjeThanks @longwave, didn't think of that.
Applied to the MR and updated the IS.
Comment #7
longwaveLooks good to me, thanks. Bumping to critical as ideally this needs to land before 10.2.0.
Comment #10
catchCommitted/pushed to 11.x and cherry-picked to 10.2.x, thanks!