Conversation
Co-authored-by: Kent C. Dodds <me+github@kentcdodds.com>
|
Cursor Agent can help with this pull request. Just |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review infoConfiguration used: defaults Review profile: CHILL Plan: Pro 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughTwo GitHub Actions workflows are updated with conditional database migration steps that execute when site cache misses occur. Each workflow gains a "🛠 Setup Database (migrations)" step running Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Run Prisma migrations before priming the cache in CI to fix deployment failures due to missing database tables.
Note
Low Risk
Workflow-only change that adds a deterministic migration step; main risk is longer CI runs or unexpected migration failures in these jobs.
Overview
Fixes CI/deployment failures caused by priming the site cache against an unmigrated database.
Both
deployment.yml(pre-deploy health check) andindex-semantic-content.ymlnow runnpx prisma migrate deploywhen the site-cache is a miss, before runningprime-cache:mocks(and before the production build in the indexing workflow).Written by Cursor Bugbot for commit 5839c7f. This will update automatically on new commits. Configure here.
Summary by CodeRabbit