Restore applied migration 0042 - #1863
Conversation
…data-display # Conflicts: # docs/production-incident-baseline.md
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
🤖 Review skipped: Repository rate limit exceeded. Free accounts are limited to 2 reviews per 4 hours per repository. Upgrade to a paid plan for unlimited reviews. |
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
Warning Review limit reached
Next review available in: 6 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
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. Comment |
Summary
0042_strength_set_activity_id_not_null.sqlto the exact bytes production appliedRoot cause
Production applied the first PR #1552 version of migration 0042, then later commits in the same PR rewrote that already-applied file before merge. The deployed ledger therefore records SHA-256
bdbd8c..., while main containedcd2800....Validation
pnpm tsx scripts/migration-policy.ts drizzle/0042_strength_set_activity_id_not_null.sqlpnpm vitest run scripts/migration-policy.test.tspnpm vitest run src/db/postgres-migrator.test.tsgit diff --checkSummary by cubic
Restores migration 0042 to exactly match what production applied, fixing the migration integrity mismatch and unblocking deployment of the climbing activity detail fix. Updates the incident baseline with the cause and recovery steps.
Migration
drizzle/0042_strength_set_activity_id_not_null.sqlto the applied version by removing the redundant constraint validation and keeping onlyALTER COLUMN activity_id SET NOT NULL.Docs
Written for commit c6f9a02. Summary will update on new commits.