Prisma · tool · fg-0292

prisma migrate dev in CI or against a shared database detects drift and wants to reset the schema

Drift detected: Your database schema is not in sync with your migration history.

Verified 2026-10-15 · Confirmed by 0 builders · Trust 50/100

Cause

migrate dev is a development command that replays history in a shadow database and offers to reset when the live schema differs. migrate deploy only applies pending migrations and never checks drift, resets, or uses a shadow database.

Fix

Use migrate deploy in CI, staging, and production, and keep migrate dev for local databases you can wipe.

Apply

npx prisma migrate deploy

Affects: Prisma ORM 6 and 7; prompt text reproduced on 7.10.0

Sources

https://www.prisma.io/docs/orm/reference/prisma-cli-reference

Have your agent know this before it fails

claude mcp add --transport http footgun https://getfootgun.com/api/mcp