Update guzzle to 6.3#29205
Closed
phil-davis wants to merge 5 commits into
Closed
Conversation
3f40d24 to
12cf9ae
Compare
Contributor
Author
|
See #29211 for a more logically squashed version of this code. |
Contributor
|
@phil-davis please pick one of the PRs, one is enough, and close the other one. Thanks. |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Update Guzzle to 6.3, and also other libraries (deleted and regenerated composer.lock)
Expecting many problems as there were API changes in that lib.
Related Issue
Motivation and Context
Guzzle 5.3 is outdated, needs update.
Also some libs used by apps will need Guzzle > 6.
How Has This Been Tested?
Types of changes
Checklist:
This is a newer version of #28063 made by cherry-pick of the commits from there, resolving conflicts and regenerating
composer.lockto (hopefully) be in sync with all the latest incomposer.json