feat: support for guzzle 8 - #427
Open
VincentLanglet wants to merge 2 commits into
Open
Conversation
Contributor
Greptile SummaryThis PR extends the SDK’s HTTP transport compatibility to Guzzle 8.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains; the previously reported unconditional calls to Guzzle exception methods are now replaced with Guzzle 8 exception types and guarded Guzzle 7 compatibility paths. Important Files Changed
Reviews (2): Last reviewed commit: "Add BC layer" | Re-trigger Greptile |
VincentLanglet
marked this pull request as ready for review
July 29, 2026 09:40
Contributor
Author
|
I saw you opened/merged recently @gjtorikian ; could you approve the workflow ? |
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.
Description
Documentation
Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.
If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.
Ref: