Skip to content

Allow Guzzle 8 - #165

Closed
simPod wants to merge 1 commit into
ActiveCampaign:mainfrom
simPod:compat/guzzle-8-postmark
Closed

Allow Guzzle 8#165
simPod wants to merge 1 commit into
ActiveCampaign:mainfrom
simPod:compat/guzzle-8-postmark

Conversation

@simPod

@simPod simPod commented Jul 24, 2026

Copy link
Copy Markdown

Summary

Allow Guzzle 8 alongside the existing Guzzle 7.8 constraint. The current client usage relies on APIs shared by both supported major versions.

@simPod
simPod force-pushed the compat/guzzle-8-postmark branch from a17cd71 to f284da2 Compare July 24, 2026 12:30
@simPod
simPod marked this pull request as ready for review July 24, 2026 12:45
ewood-ac added a commit that referenced this pull request Aug 6, 2026
Guzzle 8 support (simPod, #165) belongs in the major rather than a patch. The
constraint widening is additive, but Guzzle 8 reclassified transport
exceptions, and this SDK re-exports Guzzle's hierarchy via @throws
GuzzleException -- with http_errors => false, the transport family is the only
one that reaches a caller. So a consumer's catch (ConnectException) around a
send silently stops matching a timeout after a composer update, with no code
change on their side. A patch release is the wrong signal for that; a major
with an upgrade note is the right one.

Tightened the floors to ^7.15.2 || ^8.0.1. simPod's ^7.8 || ^8.0 admits Guzzle
8.0.0 and 7.x below 7.15.2, both affected by GHSA-v5mv-p594-2x33 (high,
host-check bypass) and GHSA-f7vp-7xgx-4w4r. 8.0.1 postdates that PR.

Verified rather than assumed: PHPStan clean and the full suite green against
both 8.0.2 and 7.15.2, and CI now runs static analysis under each major so the
claim keeps being tested.
@ewood-ac

ewood-ac commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

This was folded into another change as I needed to address error handling with some Guzzle changes.

@ewood-ac ewood-ac closed this Aug 6, 2026
@simPod
simPod deleted the compat/guzzle-8-postmark branch August 6, 2026 10:32
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.

2 participants