Update lock

[abnegate]

Summary by CodeRabbit

• Chores
  • Upgraded the underlying database dependency to the latest major version (1.x), bringing security patches, performance optimizations, and broader compatibility with modern environments.
  • No functional or UI changes are expected; users may experience improved stability and reliability.
  • This maintenance update aligns the app with current platform standards and lays groundwork for future enhancements. No action is required from users.

[coderabbitai]

Walkthrough

Dependency constraint in composer.json updated: utopia-php/database from "0.." to "1.*". No other changes.

Changes

Cohort / File(s)	Summary
Dependency Update composer.json	Bumped require constraint for utopia-php/database from "0.*.*" to "1.*".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my whiskers, nibble on a byte,
A version hops ahead into the light.
From zero’s meadow to one’s clear glade,
Our deps align, the path now paved.
Thump-thump! I stamp—upgrade delight.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore-update-db

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

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

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

composer.json (1)

29-29: Confirm Utopia Database upgrade to v1.x and audit for breaking changes

composer.lock already resolves utopia-php/database to v1.0.0. Next steps:

• Manually audit all uses of Utopia\Database APIs (Query, Document, Collection, Permission, Role, etc.)—especially under src/Migration and tests—to catch any BC changes in 1.x.
• Run the full test suite and static analysis to surface compilation or runtime errors.
• Optionally tighten your version constraint to express SemVer intent:

-        "utopia-php/database": "1.*",
+        "utopia-php/database": "^1.0",

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c478555 and bb64a8e.

⛔ Files ignored due to path filters (1)

• composer.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• composer.json (1 hunks)

🔇 Additional comments (2)

composer.json (2)

35-37: Potential Composer conflict: phpunit 11 requires PHP ≥ 8.2 but platform is set to 8.1.

This mismatch can break installs in CI even if unrelated to this PR.

Two viable fixes (choose one):

• Raise platform PHP to 8.2
• Or downgrade PHPUnit to 10.*

Diff options:

Option A (raise platform):

-        "php": "8.1"
+        "php": "8.2"

Option B (downgrade PHPUnit):

-        "phpunit/phpunit": "11.*",
+        "phpunit/phpunit": "10.*",

Also applies to: 42-44

---

24-33: Cross-package compatibility verification required

We’ve upgraded to "utopia-php/database": "1.*" alongside

• "utopia-php/framework": "0.33.*"
• "utopia-php/storage": "0.18.*"

No public documentation or migration guide confirms that database v1 is compatible with framework 0.33.x or storage 0.18.x. In practice, Composer may downgrade or fail if any package still expects database 0.x.

Please verify before merging:

• Review the changelogs and any upgrade notes on the utopia-php/database GitHub repo.
• Run integration or smoke tests covering framework and storage adapters.
• If v1 compatibility is not confirmed, consider locking database at 0.x or updating framework/storage once official support for v1 is released.