Join the discussion on Telegram
Why this matters
backend/prisma/migrations/migration_lock.toml contains:
but the datasource in backend/prisma/schema.prisma is PostgreSQL (provider = "postgresql"), and every migration uses Postgres-only SQL (ADD CONSTRAINT, multi-column ALTER TABLE ... ADD COLUMN). Prisma validates the lock-file provider against the datasource on every migrate dev / migrate deploy and aborts with a provider-mismatch error when they differ.
This is production-blocking: render.yaml runs npm run prisma:deploy (= prisma migrate deploy) as its startCommand, and backend/package.json exposes both prisma:migrate (migrate dev) and prisma:deploy (migrate deploy). The only reason CI is green is that CI uses prisma db push instead of migrate, which ignores the lock file — so the breakage is invisible until a real deploy.
Acceptance criteria
Files to touch
backend/prisma/migrations/migration_lock.toml
Out of scope
- The duplicate pause-state-field migration collision (tracked in its own issue).
- Switching CI from
db push to migrate deploy.
Join the discussion on Telegram
Why this matters
backend/prisma/migrations/migration_lock.tomlcontains:but the datasource in
backend/prisma/schema.prismais PostgreSQL (provider = "postgresql"), and every migration uses Postgres-only SQL (ADD CONSTRAINT, multi-columnALTER TABLE ... ADD COLUMN). Prisma validates the lock-file provider against the datasource on everymigrate dev/migrate deployand aborts with a provider-mismatch error when they differ.This is production-blocking:
render.yamlrunsnpm run prisma:deploy(=prisma migrate deploy) as its startCommand, andbackend/package.jsonexposes bothprisma:migrate(migrate dev) andprisma:deploy(migrate deploy). The only reason CI is green is that CI usesprisma db pushinstead ofmigrate, which ignores the lock file — so the breakage is invisible until a real deploy.Acceptance criteria
provider = "postgresql"inbackend/prisma/migrations/migration_lock.toml.npx prisma migrate deployruns cleanly against a fresh Postgres database (in tandem with the duplicate-migration fix tracked separately).prisma migrate statusreports no drift / no provider error.Files to touch
backend/prisma/migrations/migration_lock.tomlOut of scope
db pushtomigrate deploy.