
prisma-cli-migrate-deploy
✓ Official★ 8by prisma · part of prisma/cursor-plugin
prisma migrate deploy
prisma migrate deploy
Inspect the full instructions your agent will receiveExpandCollapse
This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.
by prisma
prisma migrate deploy
npx skills add https://github.com/prisma/cursor-plugin --skill prisma-cli-migrate-deploy
Download ZIPGitHub8
Command
prisma migrate deploy
What It Does
-
Applies all pending migrations from
prisma/migrations/ -
Updates
_prisma_migrationstable -
Does NOT generate new migrations
-
Does NOT run seed scripts
-
Safe for CI/CD and production
Options
Option Description
--schema Custom path to your Prisma schema
--config Custom path to your Prisma config file
When to Use
-
Production deployments
-
Staging environments
-
CI/CD pipelines
-
Any non-development environment
Examples
Basic deployment
prisma migrate deploy
In CI/CD pipeline
# GitHub Actions example
- name: Apply migrations
run: npx prisma migrate deploy
env:
DATABASE_URL: ${{ secrets.DATABASE_URL }}
Docker deployment
# Run migrations before starting app
CMD npx prisma migrate deploy && node dist/index.js
Comparison with migrate dev
Feature migrate dev migrate deploy Creates migrations Yes No Applies migrations Yes Yes Detects drift Yes No Prompts for input Yes No Uses shadow database Yes No Safe for production No Yes Resets on issues Prompts Fails
Production Workflow
Development: Create migrations locally
prisma migrate dev --name add_feature
Commit: Include migration files in version control
git add prisma/migrations
git commit -m "Add feature migration"
Deploy: Apply in production
prisma migrate deploy
Error Handling
Failed migration
If a migration fails, migrate deploy exits with error. The failed migration is marked as failed in _prisma_migrations.
To fix:
-
Resolve the issue (fix SQL, database state, etc.)
-
Mark as resolved:
prisma migrate resolve --applied <migration_name> -
Re-run:
prisma migrate deploy
Check status first
prisma migrate status
Shows pending and applied migrations before deploying.
Best Practices
-
Always run
migrate statusbeforemigrate deployin CI -
Have a rollback plan (backup before migrations)
-
Test migrations in staging first
-
Never use
migrate devin production
# GitHub Actions example
- name: Apply migrations
run: npx prisma migrate deploy
env:
DATABASE_URL: ${{ secrets.DATABASE_URL }}Run this in your project — your agent picks the skill up automatically.
prisma migrate deploy
Applies pending migrations in production/staging environments.
Configuration
Ensure prisma.config.ts has the production database URL:
import 'dotenv/config'
import { defineConfig, env } from 'prisma/config'
export default defineConfig({
datasource: {
url: env('DATABASE_URL'),
},
})
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.