Developer Documentation

Migration Checklist

Prisma migrations should be additive where possible and must not drop user data without explicit approval.

Use this when...

Use this when you need step-by-step confirmation before or after an operation.

Prisma migrations should be additive where possible and must not drop user data without explicit approval.

Use pnpm db:generate, pnpm db:migrate:status, and seed verification after schema changes. For local failed migrations, inspect Prisma output, confirm Docker/PostgreSQL is running, avoid destructive resets unless the owner explicitly approves them, and prefer pnpm db:migrate:deploy plus status checks for non-interactive verification.

Developer Details
Source
apps/docs/content/engineering-quality/migration-checklist.md
Owner
Module Owner
Status
Current
Module
Developer Documentation
Related route
None