Skip to content
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

Update to Guzzle 7 #143

Merged
merged 1 commit into from
Sep 14, 2020
Merged

Update to Guzzle 7 #143

merged 1 commit into from
Sep 14, 2020

Conversation

keithbrink
Copy link
Contributor

See #141

@IcyApril IcyApril merged commit 7db3d6e into cloudflare:master Sep 14, 2020
@keithbrink keithbrink deleted the patch-1 branch September 14, 2020 15:55
@yellow1912
Copy link

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.

@stayallive
Copy link

I agree with the above, but I would also like to see a Guzzle 7 release if possible (with or without Guzzle 6 support) 👍

@alexortizrosado
Copy link

Thanks for adding Guzzle 7 support! Any ideas when this will be released (and not only available as dev-master)?

@aalwash
Copy link

aalwash commented Dec 20, 2022

I don't understand, if it was that easy to upgrade tom ^6.2.2 -> ^7.0 without any code changes
Why not making them run together? ^6.2.2 | ^7.0?

Now you're required to upgrade to guzzle7, before you can upgrade the Cloudflare packages to 1.1.7 (from 1.1.3)
Doesn't make any sense that a minor upgrade (1.1.3 -> 1.1.7) has such a huge major guzzle upgrade dependency

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.

None yet

6 participants