●Change8

6.5.0

Breaking Changes
📦 prismaView on GitHub →
⚠ 1 breaking✨ 5 features🐛 1 fixes⚡ 1 deprecations🔧 6 symbols

Summary

Prisma 6.5.0 removes interactive database reset prompts in favor of explicit commands and introduces Prisma Studio support for the new prisma.config.ts configuration file.

⚠️ Breaking Changes

  • Automatic database reset prompts have been removed from the migrate command. If a migration cannot be applied cleanly, the CLI will now exit with an error instead of asking to reset. To reset the database, you must now run 'prisma migrate reset' explicitly.

Migration Steps

  1. If your CI/CD or local workflow relied on the interactive reset prompt during 'prisma migrate', update your scripts to use 'prisma migrate reset' when a reset is required.
  2. Update 'prisma.config.ts' to use either the 'defineConfig' helper from 'prisma/config' or the 'PrismaConfig' type from 'prisma' instead of the deprecated '@prisma/config' package.

✨ New Features

  • Added support for 'prisma.config.ts' in Prisma Studio, including driver adapter support via the 'studio' block.
  • The '$on' client method now returns the Prisma Client instance, allowing for method chaining with '$extends'.
  • Added ability to filter out spans in 'PrismaInstrumentation'.
  • Binaries can now be loaded from a local network.
  • Improved type safety for the 'AtLeast' utility type.

🐛 Bug Fixes

  • Resolved a race condition in the NextJS monorepo plugin.

🔧 Affected Symbols

PrismaClient.$onPrismaClient.$extendsPrismaConfigdefineConfigPrismaInstrumentationAtLeast

⚡ Deprecations

  • The '@prisma/config' package is being superseded by exports from the main 'prisma' package for defining configuration.