Skip to content

Allow guzzlehttp/psr7 ^2.7 compatibility #40

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sofian-io
Copy link

Laravel projects use newer psr7 versions; this patch improves compatibility

Signed-off-by: Sofian Mourabit info@sofian.io

@svenzik
Copy link
Contributor

svenzik commented May 12, 2025

Hello,

could you clarify the issue with the current version notation in composer.json ("guzzlehttp/psr7": "^2.6.0") and explain how this patch improves compatibility?

The recommended operator for maximum interoperability when writing library code is a Caret Version Range.

Running composer update on main branch will include the same versions that you have in your PR:

Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 3 updates, 0 removals
  - Upgrading guzzlehttp/psr7 (2.7.0 => 2.7.1)
  - Upgrading myclabs/deep-copy (1.13.0 => 1.13.1)
  - Upgrading phpunit/phpunit (10.5.45 => 10.5.46)
Writing lock file

Would you also mind providing the specific steps to reproduce the issue you're encountering, when using notation "^2.6.0"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants