Update lock

[abnegate]

Summary by CodeRabbit

• Chores
  • Updated the database library dependency to the 1.x series.
  • Delivers upstream stability, performance, and security improvements from the latest major release.
  • Maintains existing public interfaces; no action required from users.
  • Improves compatibility with newer environments while preserving current behavior.
  • No feature changes expected; this is an under‑the‑hood dependency refresh.

[coderabbitai]

Walkthrough

Updated composer.json dependency constraint for utopia-php/database from 0.. to 1.* in the require block. No code changes or public API alterations noted.

Changes

Cohort / File(s)	Summary
Dependencies composer.json	Bumped utopia-php/database requirement from 0.. to 1.* in require section.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A hop, a bump, a tidy nudge—
From zero lanes to one we trudge.
Composer hums, the fields align,
Carrots counted, versions fine.
Thump-thump—ship it! 🥕✨

✨ 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 (2)

composer.json (2)

25-25: Prefer caret constraint for semver clarity and Composer best practices

Use ^1.0 instead of 1.*. Functionally equivalent for 1.x but caret is the recommended operator and reads clearer in semver contexts.

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

---

25-25: Plan for potential breaking changes moving from 0.x to 1.x

Major bump suggests possible breaking changes. Validate that your codebase doesn’t rely on removed/changed APIs from utopia-php/database 0.x.

Suggested steps:

• Review the v1 migration/release notes for utopia-php/database.
• Run your test suite after a full dependency update:
  • composer update utopia-php/database --with-all-dependencies
  • phpunit
    I can help compile a checklist of API surface areas to verify if you share where this package is used (files or namespaces).

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a0d6421 and 899feb6.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• composer.json (1 hunks)

🔇 Additional comments (1)

composer.json (1)

25-25: Verify PHP Compatibility of utopia-php/database v1 with php >= 8.0

The automated Packagist lookup didn’t surface the PHP requirement for the latest stable 1.x release. Please manually confirm:

• Visit https://packagist.org/packages/utopia-php/database
• Locate the newest stable 1.x version (e.g. “1.​2.​3”)
• Check its “require → php” constraint

If it specifies “>= 8.1” (or higher), bump your project’s PHP requirement in composer.json (and adjust your CI matrix) accordingly.