7.2.0
Breaking Changes📦 prismaView on GitHub →
⚠ 1 breaking✨ 4 features🐛 6 fixes🔧 11 symbols
Summary
Prisma 7.2.0 introduces a new SQL commenter plugin, flexible URL configuration for migration commands, and runtime-aware initialization for Bun, alongside critical fixes for byte upserts and error reporting.
⚠️ Breaking Changes
- Removal of legacy byte array representation for byte upserts. This may change how raw byte data is handled during upsert operations.
Migration Steps
- If using byte upserts, verify that your byte data handling aligns with the removal of the legacy representation.
- If using 'prisma version --json' in scripts, ensure they are prepared for clean stdout output.
✨ New Features
- Added 'sqlcommenter-query-insights' plugin to support query insights metadata.
- Added '--url' parameter for 'db pull', 'db push', and 'migrate dev' commands for flexible connection configuration.
- Allowed 'prisma generate' and other config workflows to proceed even when URLs are undefined.
- Customized 'prisma init' output based on the detected JS runtime (Bun vs others).
🐛 Bug Fixes
- Converted 'DataMapperError' into a 'UserFacingError' for clearer error reporting.
- Improved Postgres adapter handling for 22P02 (invalid-text-representation) errors.
- Fixed byte upserts by removing legacy byte array representation.
- Fixed multibyte UTF-8 character splitting across chunk boundaries in byline processing.
- Ensured 'prisma version --json' emits only JSON to stdout.
- Resolved Studio connection issues in the VS Code extension/language tools.
🔧 Affected Symbols
DataMapperErrorprisma initprisma generateprisma versiondb pulldb pushmigrate devadapter-pgadapter-neonadapter-pgpsqlcommenter-query-insights