●Change8

v8.0.0-rc.4

Breaking Changes
📦 prismaView on GitHub →
⚠ 1 breaking🐛 2 fixes🔧 7 symbols

Summary

The transition period for the old ORM config is over, and two fixes land for the consolidated `prisma` CLI stack. Most projects require a config migration to the new `prisma.config.ts` format.

⚠️ Breaking Changes

  • The deprecated config fallbacks are gone. The CLI no longer reads `prisma-next.config.ts` and no longer accepts the flat (un-nested) config shape. The only config read is `prisma.config.ts` in the envelope shape. The workspace `prisma-next` binary is retired; the unified CLI runs the ORM commands at the top level.

Migration Steps

  1. Rename `prisma-next.config.ts` to `prisma.config.ts`.
  2. Wrap your ORM options in `definePrismaConfig({ orm: ormConfig({ … }) })`.
  3. Keep `import 'dotenv/config'` if your config reads `process.env`.
  4. Projects created before rc.2 need the config migration. Projects scaffolded by rc.2+ `init` need nothing.

🐛 Bug Fixes

  • `contract emit` no longer crashes after writing its artifacts when the project root is a relative path.
  • `init` scaffolds `definePrismaConfig` instead of the deprecated `defineConfig` alias.

Affected Symbols

`prisma-next.config.ts``prisma.config.ts``definePrismaConfig``defineConfig``@prisma/cli-engine``@prisma/orm-postgres/config``validateContractDeps()`