Restore applied migrations 0043-0045 - #1864
Conversation
…data-display # Conflicts: # docs/production-incident-baseline.md
|
🤖 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. |
|
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. |
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.
📝 WalkthroughWalkthroughThis PR restores migrations ChangesSchema hardening and migration restoration
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 1 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (1 passed)
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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/production-incident-baseline.md`:
- Around line 15186-15192: Add direct primary-source links to the documentation
paragraph describing migrations 0042–0045, citing PR `#1552` for the
production-applied bytes and the ledger comparison or test evidence for the
73-entry audit and eight accepted hash variants. Keep the existing factual
claims unchanged while making each restoration and audit assertion independently
verifiable.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: d9968471-4cf1-4485-8843-2d470172295b
📒 Files selected for processing (4)
docs/production-incident-baseline.mddrizzle/0043_tighten_activity_strength_set_invariants.sqldrizzle/0044_tighten_fk_delete_rules.sqldrizzle/0045_check_constraints_and_activity_active_index.sql
|
🤖 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. |
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
Summary
0043–0045to the exact bytes production appliedRoot cause
PR #1552 deployed its first migration versions before later commits rewrote
0042–0045. Production therefore recorded the initial hashes while main retained different bytes. PR #1863 restored0042; this completes the same four-file repair.Validation
0042–0045SHA-256 values match the production ledger exactlypnpm tsx scripts/migration-policy.ts drizzle/0042_strength_set_activity_id_not_null.sql drizzle/0043_tighten_activity_strength_set_invariants.sql drizzle/0044_tighten_fk_delete_rules.sql drizzle/0045_check_constraints_and_activity_active_index.sqlpnpm vitest run scripts/migration-policy.test.ts src/db/postgres-migrator.test.ts(33 passing)git diff --checkSummary by cubic
Restores migrations 0043–0045 to exactly match production so the migrator accepts history and deployments can proceed, unblocking the climbing activity display fix.
drizzle/0043–0045with the exact bytes recorded in production, completing the0042–0045restoration.0042was accepted and0043required the complete set.Written for commit e37923d. Summary will update on new commits.
Summary by CodeRabbit
Bug Fixes
Documentation