bump utopia database version

[ArnabChatterjee20k]

Summary by CodeRabbit

• Chores
  • Adjusted a core database dependency to the 1.x line to align with platform compatibility requirements. This change focuses on stability and predictable behavior across environments. No new features or UI changes are included, and existing functionality should continue to work as before. If you integrate with external database features, no configuration changes are required.

[coderabbitai]

Walkthrough

The dependency constraint for utopia-php/database in composer.json was changed from "2." to "1.". No other files or fields were modified.

Changes

Cohort / File(s)	Summary
Composer dependency update composer.json	Updated require constraint for utopia-php/database from "2.*" to "1.*"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update lock #107 — Also adjusts composer.json to use utopia-php/database version "1.*", indicating alignment on dependency versioning.

Suggested reviewers

• abnegate

Pre-merge checks (3 passed)

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The current title succinctly indicates that the pull request updates the utopia database version, which aligns with the main change of modifying the composer.json dependency and is both concise and directly related to the content of the changeset.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Poem

I hop through deps with careful cheer,
From two to one, we shift the gear.
A nibble here, a tweak so slight—
Composer hums, the build feels right.
With whiskers twitching, I approve this run—
Downversion done, now back to fun! 🐇

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch spatial-attribute-support

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

composer.json (1)

24-33: Prefer caret constraints over wildcards for predictability

Using ^ ranges communicates intent and avoids unexpectedly allowing non-stable tags if stability flags change. Consider:

-    "appwrite/appwrite": "15.*",
-    "utopia-php/database": "1.*",
-    "utopia-php/storage": "0.18.*",
+    "appwrite/appwrite": "^15.0",
+    "utopia-php/database": "^1.0",   // or ^0.x if staying on Utopia 0.x
+    "utopia-php/storage": "^0.18",

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6fb6f8f and 1fd5c65.

⛔ 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)

29-33: No conflict in Utopia dependencies; resolve as-is
composer.lock shows utopia-php/database@1.4.4 requiring framework 0.33.* (not 1.0.), and storage@0.18. is compatible with framework 0.., so pinning database to "1." alongside framework "0.33." is valid.