whitelist drizzle betas

[kibertoad]

Changes

try to allow betas

Checklist

• Apply one of following labels; major, minor, patch or skip-release
• I've updated the documentation, or no changes were necessary
• I've updated the tests, or no changes were necessary

AI Assistance Tracking

We're running a metric to understand where AI assists our engineering work. Please select exactly one of the options below:

Mark "Yes" if AI helped in any part of this work, for example: generating code, refactoring, debugging support,
explaining something, reviewing an idea, or suggesting an approach.

• Yes, AI assisted with this PR
• No, AI did not assist with this PR

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: lokalise/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: d9d5755d-dd1a-4f69-a0bb-d230d06a199a

📥 Commits

Reviewing files that changed from the base of the PR and between 20a7d79 and 484088d.

📒 Files selected for processing (1)

• packages/app/drizzle-utils/package.json

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated dependency version constraints to support broader compatibility with different versions.

Walkthrough

This change updates the peerDependencies version constraint for drizzle-orm in the drizzle-utils package. The constraint was simplified from an explicit allowlist format that only permitted versions <2.0.0, 1.0.0-beta.19, or 1.0.0-beta.20 to a more flexible range that now accepts <1.0.0 or >=1.0.0-beta.19 <2.0.0. This broadens the range of compatible drizzle-orm versions that can be used with the package.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'whitelist drizzle betas' is partially related to the changeset but uses vague terminology. The change actually modifies version constraints to allow beta versions, but 'whitelist' is imprecise for describing version range specifications.	Consider a more specific title like 'Allow drizzle-orm beta versions in peerDependencies' to clearly convey the version constraint modification.
Description check	❓ Inconclusive	The description 'try to allow betas' is very vague and doesn't clearly explain what was changed, why, or how the modification allows beta versions. While the checklist is completed, the actual description lacks specificity and detail.	Expand the description to explain which package is affected, what the old vs new version constraints are, and the rationale for allowing beta versions.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/support-betas

---

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