●Change8

Migrating to Prisma 7.3.0

Version 7.3.0 introduces 2 breaking changes. This guide details how to update your code.

Released: 1/21/2026

2
Breaking Changes
3
Migration Steps
8
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

generator client@map$executeRaw$queryRaw@prisma/adapter-mssql@prisma/better-sqlite3relationJoinsJSONB_BUILD_OBJECT

Breaking Changes

●Issue #1

The behavior of `@map` enums has been reverted to v6.19.0 due to issues introduced in v7.0 where the generated enum value came from the value passed to `@map`. Users relying on the v7.0 behavior must adjust their schema or code.

●Issue #2

When using `relationJoins` with BigInt fields in PostgreSQL, BigInt values were previously returned as JSON numbers, leading to precision loss in JavaScript after `parse` if the value exceeded `Number.MAX_SAFE_INTEGER`. This is fixed by casting BigInt columns to `::text` in `JSONB_BUILD_OBJECT` calls, meaning BigInts are now returned as JSON strings.

Migration Steps

  1. 1
    If you rely on the v7.0 behavior for `@map` enums, you must update your schema or code as this behavior has been reverted to v6.19.0.
  2. 2
    If using `@prisma/better-sqlite3`, upgrade to v7.3.0 to receive the pinned version that avoids SQLite bugs.
  3. 3
    Optionally, configure `compilerBuild = "fast"` or `compilerBuild = "small"` in your `generator client` block in `schema.prisma` to tune query compilation performance vs. client bundle size.

Release Summary

Prisma 7.3.0 introduces performance tuning via the `compilerBuild` option for the ORM client and allows raw queries to bypass the query compiler. This release also reverts a breaking change related to mapped enums and fixes BigInt precision issues in PostgreSQL JSON aggregations.

Need More Details?

View the full release notes and all changes for Prisma 7.3.0.

View Full Changelog