prisma-cli

Run prisma migrate dev --name your_migration_name during development to create and apply a migration from schema changes. For production, commit the migration files and run prisma migrate deploy in your CI/CD pipeline.

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 rollback capability and drift detection, suited for team development and production paths.

In Prisma 7, run prisma generate explicitly after migrate dev, db push, or migrate reset when you need refreshed client output. Seeding also requires running prisma db seed explicitly after migrations.

Use bunx --bun before Prisma commands, such as bunx --bun prisma generate. Without the --bun flag, the CLI falls back to Node.js because of its shebang.

Resolve the underlying issue, then run prisma migrate resolve --rolled-back <migration_name> to mark it as failed, or --applied if it actually succeeded. Afterward, re-run prisma migrate deploy to continue applying pending migrations.

Avoid db push in production, team collaboration, or when you need rollback capability, since it creates no migration history. Use migrate dev and migrate deploy instead for trackable, reversible schema changes.