Support Guzzle 8 - #34
Open
esetnik wants to merge 1 commit into
Open
Conversation
esetnik
marked this pull request as ready for review
August 5, 2026 16:37
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.
Summary
guzzlehttp/guzzle ^8.0while preserving^7.8Closes #33.
Validation
Validated on PHP 8.5.9 with Composer 2.10.2.
Guzzle 8
guzzlehttp/guzzle 8.0.1,guzzlehttp/promises 3.0.0, andguzzlehttp/psr7 3.0.0GuzzleHttp\Client+MockHandlersmoke covered synchronous and asynchronous calls, 4xx exception translation, response deserialization, JSON model bodies, Basic auth, query construction, and multipartSplFileObjectuploadGuzzle 7
composer update \ --with 'guzzlehttp/guzzle:^7.8' \ --with-all-dependencies --no-interactionguzzlehttp/guzzle 7.15.2This repository does not currently contain an automated test suite, static-analysis dependency, Composer test script, or CI workflow. Strict Composer validation also retains the pre-existing warning for the fixed
versionfield; validation passes when that unrelated check is omitted.