prisma-cli

Run prisma migrate dev --name your_migration_name during development to generate and apply a migration from schema changes. For production, commit the migration files and run prisma migrate deploy, which applies pending migrations without prompts.

db push syncs the schema directly without creating migration files or tracking history, making it faster for prototyping. migrate dev creates versioned migration files with drift detection and rollback capability, which is better for team collaboration and production paths.

In current Prisma releases you should run prisma generate and prisma db seed explicitly after migrate dev when you need refreshed client output or seed data. Configure the seed command under migrations.seed in prisma.config.ts.

Resolve the underlying issue, then run prisma migrate resolve --rolled-back <migration_name> to mark it as rolled back, and re-run prisma migrate deploy. Use prisma migrate status first to inspect which migrations failed or are pending.

Yes, but always add the --bun flag, for example bunx --bun prisma generate, so Prisma runs with the Bun runtime. Without it, the CLI falls back to Node.js because of its shebang.

Avoid db push in production, in team environments needing trackable changes, and whenever you need rollback capability, since it creates no migration history. Use migrate dev and migrate deploy instead for those scenarios.