Update to Guzzle 7#143
Merged
Merged
Conversation
|
Why not using something like this: "guzzlehttp/guzzle": "^6.0 || ^7.0" to support both versions if the library does not require Guzzle 7 in specific. |
|
I agree with the above, but I would also like to see a Guzzle 7 release if possible (with or without Guzzle 6 support) 👍 |
Closed
|
Thanks for adding Guzzle 7 support! Any ideas when this will be released (and not only available as dev-master)? |
|
I don't understand, if it was that easy to upgrade tom ^6.2.2 -> ^7.0 without any code changes Now you're required to upgrade to guzzle7, before you can upgrade the Cloudflare packages to 1.1.7 (from 1.1.3) |
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.
See #141