Repository navigation
chore(deps): allow utopia-php/client 0.3.x - #10
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Greptile SummaryWidens the supported
Confidence Score: 5/5The PR appears safe to merge because the widened constraint preserves the existing valid resolution while permitting downstream consumers to select the newer compatible release. Composer can continue resolving the locked 0.2.2 release, and environments unable to satisfy a newer release's transitive platform requirements can retain a compatible 0.2.x version. Important Files Changed
Reviews (1): Last reviewed commit: "chore(deps): allow utopia-php/client 0.3..." | Re-trigger Greptile |
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.
utopia-php/client0.3.0 exists only to move that package ontoutopia-php/pools2.x — itssrc/is byte-identical to 0.2.3, so nothing here needs to change beyond widening the constraint.Because this SDK pins
^0.2.2, it currently forcesclient(and transitivelypools) to stay on the old major, which blocks appwrite/appwrite from upgrading to pools 2.composer.lockis deliberately untouched:client0.2.2 still satisfies the widened constraint, so CI keeps testing against the currently locked version while downstream consumers become free to resolve 0.3.x.🤖 Generated with Claude Code