You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The version number of the psr-http-message-bridge package has been separate from the main Symfony releases up until now, but looking at some changes in the recipe and the repository it looks like it's going to be included from version 6.4 on.
When I set extra.symfony.require in my composer.json to ^6.0 and there's a package that requires something like "symfony/psr-http-message-bridge": "^1.2||^2.0" Flex is unable to resolve the dependencies because it thinks it should resolve to psr-http-message-bridge version 6.4 (which isn't released yet at the time of writing) with the message: found symfony/psr-http-message-bridge[v1.2.0, v1.3.0, v2.0.0, ..., v2.3.1] but these were not loaded, likely because it conflicts with another require
Updating the constraint in composer.json to 6.3.* does fix the problem, but I imagine others will encounter this when 6.4 releases and are using external packages that haven't updated their dependencies.
The text was updated successfully, but these errors were encountered:
Hi there,
The version number of the psr-http-message-bridge package has been separate from the main Symfony releases up until now, but looking at some changes in the recipe and the repository it looks like it's going to be included from version 6.4 on.
When I set
extra.symfony.require
in my composer.json to^6.0
and there's a package that requires something like"symfony/psr-http-message-bridge": "^1.2||^2.0"
Flex is unable to resolve the dependencies because it thinks it should resolve to psr-http-message-bridge version 6.4 (which isn't released yet at the time of writing) with the message:found symfony/psr-http-message-bridge[v1.2.0, v1.3.0, v2.0.0, ..., v2.3.1] but these were not loaded, likely because it conflicts with another require
Updating the constraint in composer.json to
6.3.*
does fix the problem, but I imagine others will encounter this when 6.4 releases and are using external packages that haven't updated their dependencies.The text was updated successfully, but these errors were encountered: