chore(deps): widen utopia-php/cache constraint to ^3.1 (accept 3.2.x)#912
Conversation
Greptile SummaryWidens the
Confidence Score: 5/5Safe to merge — purely a dependency constraint widening with no application code changes. The change is limited to relaxing a Composer version constraint and bumping the resolved lock file entry. The new constraint No files require special attention. Important Files Changed
Reviews (2): Last reviewed commit: "chore(deps): widen utopia-php/cache cons..." | Re-trigger Greptile |
There was a problem hiding this comment.
Pull request overview
This PR updates the project’s Composer dependency constraint for utopia-php/cache to allow compatible minor versions while keeping the 3.1 minimum, and refreshes the lockfile to use 3.2.0. This aligns the dependency range with other components already using caret constraints and unblocks downstream adoption of cache 3.2.x.
Changes:
- Widen
utopia-php/cacherequirement from3.1.*to^3.1incomposer.json. - Update
composer.lockto resolveutopia-php/cacheto3.2.0and refresh related metadata/hash.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| composer.json | Widens utopia-php/cache constraint to accept compatible 3.x minors while keeping a 3.1 floor. |
| composer.lock | Updates the locked utopia-php/cache package version and associated references to 3.2.0. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
3.1.* excluded the 3.2.0 release (purge-tombstone lease, backward-compatible and opt-in). ^3.1 keeps the 3.1 floor the query/getDocument lease needs while accepting compatible minors, matching the ^3.0 constraint the rest of the ecosystem (server-ce, domains, vcs) already uses. Unblocks consumers that need cache 3.2.0. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
b9973c1 to
eedf0ee
Compare
|
Warning Review limit reached
Next review available in: 54 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
3.1.*excludes utopia-php/cache 3.2.0 (the opt-in, backward-compatible purge-tombstone lease). Widen to^3.1— keeps the 3.1 floor the query/getDocumentlease relies on, while accepting compatible minors, matching the^3.0constraint server-ce / domains / vcs already use.Unblocks appwrite-labs/cloud from adopting cache 3.2.0 (the getDocument-path lost-update fix). Lock bumped to 3.2.0 for consistency.
🤖 Generated with Claude Code