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

[10.x] Remove workarounds for old Guzzle versions #47084

Merged
merged 1 commit into from
May 15, 2023

Conversation

GrahamCampbell
Copy link
Member

We already require Guzzle ^7.5, which means all the newer (like 3 or 4 years old at this point) class methods are necessarily available.

@nunomaduro
Copy link
Member

@GrahamCampbell What do you think about including "conflict", to ensure people are indeed using a Guzzle version that is compatible with Laravel?

    "conflict": {
        "guzzlehttp/guzzle": "<7.6"
    },

@taylorotwell taylorotwell merged commit ab18c4a into 10.x May 15, 2023
@taylorotwell taylorotwell deleted the remove-old-guzzle-hacks branch May 15, 2023 14:58
@GrahamCampbell
Copy link
Member Author

GrahamCampbell commented May 15, 2023

What do you think about including "conflict"

I typically don't like this, because it stops someone using whatever version of Guzzle they want to use, unrelated to using it through Laravel.

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.

4 participants