Add support for Guzzle 8#222
Merged
Merged
Conversation
Contributor
Author
|
Hi maintainers 👋 First of all, thank you for maintaining this package — it has been very useful for us. We’ve opened this PR to add Guzzle 8 support by relaxing the Composer constraint to Would you mind reviewing and approving this MR when you have a moment? Happy to adjust anything if needed. Thanks again for your work on |
HecFranco
force-pushed
the
feature/guzzle-8-support
branch
from
July 22, 2026 10:47
1b38c78 to
47ee982
Compare
Allow guzzlehttp/guzzle ^8.0 alongside ^7.0 so consumers can upgrade the HTTP client stack.
HecFranco
force-pushed
the
feature/guzzle-8-support
branch
from
July 22, 2026 10:47
47ee982 to
1a5c34d
Compare
Owner
|
Thanks for your PR! 🙌🏻 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
guzzlehttp/guzzle^8.0alongside^7.0so consumers can upgrade their HTTP client stack without a fork or constraint conflict.Context
Guzzle 8 is available and some projects (including ours) are moving to it. The package currently requires
^7.0only, which blocks that upgrade path even though the library usage of Guzzle remains compatible.Changes
composer.json:guzzlehttp/guzzle→^7.0 || ^8.0Test plan
composer update guzzlehttp/guzzle:^7.0) and run the test suitecomposer update guzzlehttp/guzzle:^8.0) and run the test suiteGoogleTranslate::trans(...)/ instancetranslate()call under both major versions