chore: drop sev from validation rule schema

[adityachoudhari26]

No description provided.

[coderabbitai]

Warning

Rate limit exceeded

@adityachoudhari26 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 29 minutes and 19 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 45190950-2f27-4f6a-a5e0-bda048b985c7

📥 Commits

Reviewing files that changed from the base of the PR and between 32bde8e and bbdbe21.

📒 Files selected for processing (4)

• packages/db/drizzle/0194_brief_longshot.sql
• packages/db/drizzle/meta/0194_snapshot.json
• packages/db/drizzle/meta/_journal.json
• packages/db/src/schema/deployment-plan.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch drop-plan-validation-severity

---

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

_{Review rate limit: 0/1 reviews remaining, refill in 29 minutes and 19 seconds.}

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

[Copilot]

Pull request overview

Removes the severity field from the policy_rule_plan_validation_opa validation-rule table schema and applies the corresponding database migration, aligning the Drizzle schema and snapshots with the updated DB shape.

Changes:

• Drop severity column from policy_rule_plan_validation_opa Drizzle schema.
• Add migration 0194_brief_longshot to drop the column in Postgres.
• Update Drizzle migration journal and snapshot metadata to reflect the new schema.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

File	Description
packages/db/src/schema/deployment-plan.ts	Removes severity column from the Drizzle table definition.
packages/db/drizzle/0194_brief_longshot.sql	Adds migration to drop severity from policy_rule_plan_validation_opa.
packages/db/drizzle/meta/_journal.json	Registers the new migration in the Drizzle journal.
packages/db/drizzle/meta/0194_snapshot.json	Updates the schema snapshot after dropping the column.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.