Add support for Guzzle 8#3294
Draft
GrahamCampbell wants to merge 1 commit into
Draft
Conversation
Member
|
Thanks for the work on this @GrahamCampbell. When is the release date for 8? |
Contributor
Author
|
I did the 7.11.0 release today, along with 6 releases in the other first-party packages with a bunch of deprecations. I'll see how that goes with feedback, and I'll be doing more evaluation of the upgrading of the most popular packages to Guzzle 8. I don't yet have a an exact release date to share. I am hoping it'll be ready early Q3. |
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
2 participants
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.
Guzzle 8 is not yet released, but once it is, getting support in the AWS SDK is important, because it would otherwise block many other projects including Laravel from supporting Guzzle 8.
#3289 already makes a forward-compatible change that makes the SDK compatible with Guzzle 8's stricter requirement that headers be strings or lists of strings. The next change to be aware of is Guzzle 8's changes to the exceptions. The
ResponseTransferExceptionexception was added specifically to accommodate the needs of the AWS SDK to want to retry this sub-class of failures, without needing to look at the handler context which is a leaky abstraction that was removed in Guzzle 8.This PR makes changes to support the old and new exception design, and adjusts version constraints to support both Guzzle 7 and Guzzle 8. By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.