Bug description
When updating from prisma 6.16.2 to 6.16.3 the migrate diff command suddenly returns exit code 1 with no other logs. AFAIK there is not like a --verbose option to help with debugging.
Severity
⚠️ Major: Breaks core functionality (e.g., migrations fail)
Reproduction
See this repo https://github.com/vdhpieter/prisma-migrate-diff-issue
Expected vs. Actual Behavior
Getting exit code 0 and the message No difference detected.. Or getting exit code 1 with more explanations.
Frequency
Consistently reproducible
Does this occur in development or production?
Only in development (e.g., CLI tools, migrations, Prisma Studio)
Is this a regression?
Yes it worked until prisma 6.16.2
Workaround
No workaround found
Prisma Schema & Queries
Not sure if it's relevant
generator client {
provider = "prisma-client-js"
output = "./__generated__"
previewFeatures = ["typedSql"]
}
generator comments {
provider = "prisma-db-comments-generator"
}
datasource db {
provider = "postgresql"
url = env("DB_URL")
}
...
Prisma Config
import { defineConfig } from "prisma/config";
export default defineConfig({
migrations: {
seed: "ts-node seed.ts",
},
});
Logs & Debug Info
No logs providen
Environment & Setup
- OS: macOS and in CI
- **Database: PostgreSQL
- **Node.js version: v24.5.0
Prisma Version
prisma : 6.16.3
@prisma/client : 6.16.3
Computed binaryTarget : darwin-arm64
Operating System : darwin
Architecture : arm64
Node.js : v24.5.0
TypeScript : 5.9.3
Query Engine (Node-API) : libquery-engine bb420e667c1820a8c05a38023385f6cc7ef8e83a (at ../../../node_modules/prisma/node_modules/@prisma/engines/libquery_engine-darwin-arm64.dylib.node)
PSL : @prisma/prisma-schema-wasm 6.16.1-1.bb420e667c1820a8c05a38023385f6cc7ef8e83a
Schema Engine : schema-engine-cli bb420e667c1820a8c05a38023385f6cc7ef8e83a (at ../../../node_modules/prisma/node_modules/@prisma/engines/schema-engine-darwin-arm64)
Default Engines Hash : bb420e667c1820a8c05a38023385f6cc7ef8e83a
Studio : 0.511.0
Preview Features : typedSql
Bug description
When updating from prisma 6.16.2 to 6.16.3 the migrate diff command suddenly returns exit code 1 with no other logs. AFAIK there is not like a
--verboseoption to help with debugging.Severity
Reproduction
See this repo https://github.com/vdhpieter/prisma-migrate-diff-issue
Expected vs. Actual Behavior
Getting exit code 0 and the message
No difference detected.. Or getting exit code 1 with more explanations.Frequency
Consistently reproducible
Does this occur in development or production?
Only in development (e.g., CLI tools, migrations, Prisma Studio)
Is this a regression?
Yes it worked until prisma 6.16.2
Workaround
No workaround found
Prisma Schema & Queries
Not sure if it's relevant
Prisma Config
Logs & Debug Info
No logs providen
Environment & Setup
Prisma Version