@prisma/client@7.10.0
Review before merging.
Release notes list 8 breaking changes: Prisma Studio now binds only to 127.0.0.1, breaking remote access to its local server.
Why this verdict
- Release notes list 8 breaking changes: Prisma Studio now binds only to 127.0.0.1, breaking remote access to its local server.Evidence
Confidence 100% · algorithm v1 · computed 2026-11-22. How verdicts work
Supply chain and security
- Malware reports
- None known (OSV)
- Known advisories
- None known (OSV)
- License
- Apache-2.0
- Install scripts
- None
- Build provenance
- Signed provenance
- Weekly downloads
- 2,015,507
Compatibility
No compatibility boundary is crossed: this is a patch or minor release on a stable major.
Breaking changes in the release notes
- Prisma Studio now binds only to 127.0.0.1, breaking remote access to its local server.“Binds explicitly to `127.0.0.1` instead of all network interfaces.”
- PostgreSQL deadlocks are now reported as error code P2034 instead of the previous code.“PostgreSQL deadlocks using SQLSTATE `40P01` are now reported as `P2034` transaction write conflicts.”
- PostgreSQL RESTRICT violations are now reported as error code P2003.“PostgreSQL `RESTRICT` violations using SQLSTATE `23001` are now reported as `P2003`, preserving an available field or constraint name.”
- The PostgreSQL adapter now includes constraint names in P2002 unique‑constraint errors.“`@prisma/adapter-pg` now preserves database constraint names when reporting unique constraint violations through `P2002`.”
- Prisma Postgres Serverless now prefers named constraints for P2002 errors, changing error details.“Prisma Postgres Serverless now prefers the named constraint for `P2002`, falling back to parsed field names when no constraint name is available.”
- SQLite adapter now converts previously unhandled SQLite result codes into typed database errors.“`@prisma/adapter-better-sqlite3` now converts previously unhandled SQLite result codes into typed database errors instead of exposing raw driver errors.”
- The full SQLITE_BUSY family is now mapped to socket timeout errors, altering error handling.“The complete `SQLITE_BUSY` family is now mapped to socket timeout errors, with numeric extended result codes preserved where available.”
- Empty or generator‑only schema files now error out with a missing datasource message instead of proceeding silently.“Empty or generator-only schema files now report `Schema must contain a datasource block` from `db pull`, `db push`, and `migrate dev`, rather than reaching the schema engine and potentially producing inconsistent errors.”
AI-extracted from the official release notes and checked against the quoted text. Read the source
1 issue mentions this version in prisma/orm within 14 days of release. See them on GitHub
Check the official release notes below for behaviour changes before merging.
Release notes
Read the Prisma changelog on Changes.Watch or the package page on npm for this version’s features and fixes.
New in this release
- Introduces a compatibility package @prisma/prisma7 for side‑by‑side Prisma 7 and Prisma 8.“This release introduces `@prisma/prisma7`, a compatibility package that lets you retain a matching Prisma 7 CLI and configuration while installing Prisma 8 in the same project.”
- Result‑extension compute callbacks now receive the current model name as a second argument.“Result-extension `compute` callbacks now receive the current model name as a typed second argument:”
- The MariaDB adapter can now accept an existing mariadb connection pool.“`@prisma/adapter-mariadb` now accepts an existing `mariadb` pool. External pools remain caller-owned unless `disposeExternalPool: true` is supplied.”
- Adds support for bracketed IPv6 addresses in mysql:// and mariadb:// connection strings.“Added support for bracketed IPv6 addresses in both `mysql://` and `mariadb://` connection strings.”
- `prisma generate` can now prompt to install Prisma's agent skills.“`prisma generate` can now offer to install Prisma's agent skills.”
- `prisma version` and `prisma version --json` now include the resolved Prisma CLI package path.“`prisma version` and `prisma version --json` now include the resolved Prisma CLI package path, making global-versus-local installation issues easier to diagnose.”
AI-extracted from the official release notes and checked against the quoted text. Read the source
Deprecations and deadlines
The maintainer has not deprecated this version on npm.
Did upgrading to 7.10.0 work for you?
Results appear once three developers have voted.