6.15.0
Breaking Changes📦 prismaView on GitHub →
⚠ 3 breaking✨ 7 features🐛 1 fixes🔧 6 symbols
Summary
Prisma 6.15.0 introduces AI safety guardrails for destructive CLI commands, simplifies Client runtime configurations, and moves the Prisma Postgres Management API to General Availability.
⚠️ Breaking Changes
- The 'node' runtime option has been removed. To fix this, update your generator configuration to use 'runtime = "nodejs"'.
- The 'deno-deploy' runtime option has been removed. To fix this, update your generator configuration to use 'runtime = "deno"'.
- The 'vercel' runtime option has been replaced. To fix this, use 'runtime = "vercel-edge"'.
Migration Steps
- Update Prisma schema generator blocks: replace 'runtime = "node"' with 'runtime = "nodejs"'.
- Update Prisma schema generator blocks: replace 'runtime = "deno-deploy"' with 'runtime = "deno"'.
- Update Prisma schema generator blocks: replace 'runtime = "vercel"' with 'runtime = "vercel-edge"'.
- Update the Prisma VS Code extension to the latest version to support new runtime validation.
✨ New Features
- AI safety guardrails: The CLI now detects AI agents (Claude Code, Gemini, Cursor, etc.) and prompts for confirmation before destructive commands like 'prisma migrate reset --force'.
- New 'vercel-edge' runtime for Prisma Client.
- Support for empty schemas: 'prisma generate' now succeeds even if the schema contains no models when using the 'prisma-client' generator.
- Prisma Postgres Management API is now Generally Available (GA), allowing programmatic provisioning of databases.
- New '--json' flag for 'npx create-db' to return database connection details in JSON format.
- Pipedream integration for Prisma Postgres.
- Support for Vercel Fluid compute via 'attachDatabasePool' and driver adapters.
🐛 Bug Fixes
- Fixed an issue where 'prisma generate' would fail if the schema contained no models when using the 'prisma-client' provider.
🔧 Affected Symbols
prisma-clientprisma-client-jsprisma migrate resetnpx create-dbPrismaClientPrismaPg