Mark psr/http-message >=2.0 supported #310
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation: Make installation on Apigee Edge module easier on Drupal 10+ projects was built with https://packagist.org/packages/drupal/core-recommended#10.1.3 that depends on https://packagist.org/packages/symfony/psr-http-message-bridge#v2.3.1.
What is the problem?
When a new clean Drupal 10+ project is created with
drupal/core-recommended
Composer picks the highest version of packages, including psr/http-message and it installs 2.0.0. Later when drupal/apigee_edge module gets installed, Composer needs convincing to downgrade to a previous version of psr/http-message because this package needs that. (Luckily the rest of the dependency chain also support 1.x.)Related: