Prisma 7.10.0

Prisma ORM 7.10.0 landed as a stable release at an awkward moment. The Prisma team is mid-flight toward Prisma 8, with the v8 release-candidate line already rolling out. So this is a maintenance release with a specific job: keep Prisma 7 maintainers from being stranded while the v8 migration plays out. Before you update, it is worth understanding exactly what this release does and what it does not do.

The Compatibility Bridge

The centerpiece is a new package called @prisma/prisma7. It lets you install Prisma 8 in a project while keeping a matching Prisma 7 CLI and configuration intact. The two run side by side instead of overwriting each other.

• Separate binaries: the v8 CLI stays as prisma; the v7 bridge is invoked as prisma7.
• Separate config namespace: v7 now prefers prisma7.config.* files, falling back to existing prisma.config.* only for compatibility. That avoids the config collision you would otherwise get with v8.
• No silent fallback: if a prisma7.config.* file exists but cannot be loaded, Prisma reports the error rather than quietly switching configs.

Pragmatic, but note the trade-off: you now have two CLIs, two config schemes, and a version pin to babysit in every project that straddles the transition. Adopt the split documentation carefully or you will end up running the wrong generator.

Studio Security Hardening

One change that is unambiguously good: Prisma Studio local server now binds to 127.0.0.1 instead of every network interface, rejects browser requests from foreign origins, and drops the wildcard CORS header. These protections are applied across Node, Bun, and Deno. Long overdue, and it closes a real exposure if you run Studio on a shared machine.

Client and Driver Fixes

Most of the release is fixes below the hood, and several of them are the kind that quietly bite teams in production.

• Nested-write P2002 errors now report the correct model name, including models using @@map and @@schema.
• Automatically batched findUniqueOrThrow() calls now reject every missing record with P2025 instead of letting later misses resolve to undefined.
• Deserialized Bytes values own standalone ArrayBuffers rather than borrowing from the shared Node.js buffer pool.
• Fluent relation queries no longer break when relation fields are literally named select or include.
• MariaDB adapter now accepts an existing pool and fixes connection leaks on commit, rollback, and failed transaction startup.

Watch These Error-Mapping Changes

Two database-error remaps can change what your code catches. PostgreSQL deadlocks (SQLSTATE 40P01) are now reported as P2034 write conflicts, and PostgreSQL RESTRICT violations (SQLSTATE 23001) are now reported as P2003. If your app currently matches on the old generic errors, audit those handlers after upgrading.

The Verdict

If you are on Prisma 7 and not touching v8 yet, this is a low-risk, worthwhile update full of real fixes, especially around unique-constraint errors and transaction cleanup, plus the Studio hardening. If you are evaluating v8, the @prisma/prisma7 bridge is precisely targeted but means managing two environments. In either case, read the error-mapping changes before you roll it out. There is nothing here that demands an immediate emergency upgrade, but there is also no strong reason to wait.