Skip to content

chore(deps): widen utopia-php/cache constraint to ^3.1 (accept 3.2.x)#912

Merged
abnegate merged 1 commit into
mainfrom
chore/allow-cache-3.2
Jul 1, 2026
Merged

chore(deps): widen utopia-php/cache constraint to ^3.1 (accept 3.2.x)#912
abnegate merged 1 commit into
mainfrom
chore/allow-cache-3.2

Conversation

@abnegate

@abnegate abnegate commented Jul 1, 2026

Copy link
Copy Markdown
Member

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/getDocument lease relies on, while accepting compatible minors, matching the ^3.0 constraint 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

Copilot AI review requested due to automatic review settings July 1, 2026 08:53
@greptile-apps

greptile-apps Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

Widens the utopia-php/cache Composer constraint from 3.1.* to ^3.1.0 and bumps the lock file to resolve at 3.2.0, unblocking adoption of the backward-compatible purge-tombstone lease and getDocument-path lost-update fix introduced in that release.

  • composer.json: Constraint changed from 3.1.* (patch-only range) to ^3.1.0 (accepts any compatible minor up to <4.0.0), matching the ^3.0 convention used by other utopia-php packages in the ecosystem.
  • composer.lock: Resolved version bumped from 3.1.0 to 3.2.0 with updated git reference and content-hash; no other packages affected.

Confidence Score: 5/5

Safe 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 ^3.1.0 correctly keeps the 3.1 floor and allows compatible minors; cache 3.2.0 is described as backward-compatible. No source files were modified.

No files require special attention.

Important Files Changed

Filename Overview
composer.json Widens utopia-php/cache constraint from 3.1.* to ^3.1.0 (accepts 3.1.x through <4.0.0)
composer.lock Lock file updated to resolve utopia-php/cache at 3.2.0 with new git ref and content-hash

Reviews (2): Last reviewed commit: "chore(deps): widen utopia-php/cache cons..." | Re-trigger Greptile

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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/cache requirement from 3.1.* to ^3.1 in composer.json.
  • Update composer.lock to resolve utopia-php/cache to 3.2.0 and 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>
@abnegate abnegate force-pushed the chore/allow-cache-3.2 branch from b9973c1 to eedf0ee Compare July 1, 2026 08:55
@coderabbitai

coderabbitai Bot commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@abnegate, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c5c40556-c734-4b2a-b71c-f8c824a890ef

📥 Commits

Reviewing files that changed from the base of the PR and between 7bbe954 and eedf0ee.

⛔ Files ignored due to path filters (1)
  • composer.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • composer.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/allow-cache-3.2

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@abnegate abnegate merged commit c279b24 into main Jul 1, 2026
22 checks passed
@abnegate abnegate deleted the chore/allow-cache-3.2 branch July 1, 2026 09:16
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