prisma-migrations

To deploy Prisma migrations safely in CI/CD, run prisma migrate deploy against your target environment database. This command applies pending migration files without generating new ones, ensuring predictable production database schema changes.

Prisma migrate dev generates new migration files and applies them to your development database, while migrate deploy only applies existing pending migrations to production. Using migrate dev in production is a risky workflow that this process explicitly prevents.

Baselining a database that predates Prisma Migrate involves marking existing schema state as applied in the _prisma_migrations table. This synchronizes your migration history so future Prisma database deployments can track and apply pending changes accurately.

Prisma database migration failures in production often stem from schema drift or running prisma migrate dev instead of migrate deploy. Troubleshooting involves checking migration status and resolving inconsistencies between your schema.prisma and the _prisma_migrations table.

To create version-controlled migration files from an updated schema.prisma, run prisma migrate dev in your development environment. This generates the migration files and applies them locally to ensure your database schema changes are consistent.