Repository navigation
fix: enforce transport limits and expand PHP security checks - #14
Closed
MudassarTariq wants to merge 4 commits into
Closed
MudassarTariq wants to merge 4 commits into
MudassarTariq wants to merge 4 commits into
Conversation
MudassarTariq
marked this pull request as ready for review
October 24, 2026 18:17
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.
Stalled responses could exceed the configured timeout, truncated responses could be accepted as complete, and diagnostics could expose API keys. This change enforces the transport limits and prepares patch release 3.0.2.
Public methods, response models and JSON/XML support are preserved. Custom Guzzle exception subclasses with incompatible constructors are normalized to the corresponding base exception; nested diagnostic causes are redacted copies. PHP engine updates remain the application host's responsibility. PHP 8.1 coverage verifies compatibility, not runtime security support.
Validation:
After the required review, merge this PR and publish v3.0.2. No production hosting change is needed for deployments that do not run PHP.