Add support for Guzzle 8 and PSR-7 / promises 3.x - #357
Conversation
|
Closes #356 |
Widen composer constraints and extract responses via method_exists so middleware stays compatible with Guzzle 7 RequestException and Guzzle 8 ResponseException.
4d08133 to
84ae2c9
Compare
|
Thank you for your time reviewing this PR! CI is green on the supported PHP/Symfony matrix. Could you please consider approving and merging when you have a moment? This would unblock projects that need Guzzle 8 (with PSR-7 / promises 3.x) while remaining compatible with Guzzle 6/7. Happy to adjust anything if needed. Thanks again! |
|
Hi @gregurco — gentle ping on this one. CI is green across the PHP/Symfony matrix. This PR is intentionally additive (keeps Guzzle 6/7 + Symfony 5) and only adds Guzzle 8 / PSR-7 3 / promises 3 support, plus a small middleware tweak so response extraction works with Guzzle 8’s exception hierarchy. I saw your draft #355, which takes a broader approach (dropping older majors / CI updates). Happy to follow whichever direction you prefer:
This is currently blocking our upgrade to Guzzle 8. Thanks for taking a look when you have a moment! |
|
@HecFranco thank you for the contribution 🙌 |
Summary
guzzlehttp/guzzle^8.0,guzzlehttp/psr7^3.0, andguzzlehttp/promises^3.0while keeping Guzzle 6/7 support.method_exists(..., 'getResponse')instead of hard-typing Guzzle 7'sRequestException, so logging and event dispatch work with Guzzle 8's exception hierarchy.Why a separate PR from #355
#355 (draft) drops Guzzle 6 and Symfony 5 and updates CI. This PR is intentionally additive: it keeps existing supported majors and only adds the runtime compatibility needed for Guzzle 8. Happy to rebase/align with #355 if you prefer that direction.
Test plan
Related issue: will link after creation.
Made with Cursor