# prisma 7.10.0

- Product: prisma (https://whatsnew.fyi/product/prisma)
- Vendor: prisma
- Date: 2026-08-25
- Version: 7.10.0
- Original notes: https://github.com/prisma/prisma/releases/tag/7.10.0
- Permalink: https://whatsnew.fyi/product/prisma/releases/7.10.0

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **added** — Introduce @prisma/prisma7 compatibility package to run Prisma 7 alongside Prisma 8 in the same project
- **added** — Support prisma7.config.* configuration files for version-specific Prisma 7 configuration
- **added** — Add prisma7 CLI command as an alias to run Prisma 7 when both versions are installed
- **changed** — Prisma Studio's local HTTP server now binds explicitly to 127.0.0.1 instead of all network interfaces
- **changed** — Prisma Studio rejects browser requests from origins other than the active localhost or 127.0.0.1 Studio URL
- **changed** — Prisma Studio no longer returns wildcard CORS headers
- **fixed** — Fixed P2002 errors from nested writes so meta.modelName identifies the model where the unique constraint violation occurred
- **fixed** — Fixed automatically batched findUniqueOrThrow() calls so every missing record rejects with P2025
- **fixed** — Parameter-chunked statements are now executed atomically in a transaction and rolled back if a later chunk fails
- **fixed** — Improved interactive transaction cleanup during $disconnect() including transactions whose driver-level startup is still in progress
- **fixed** — Prevented transaction cleanup failures after a timeout or backend termination from becoming unhandled promise rejections
- **fixed** — Fixed fluent relation queries when relation fields are literally named select or include
- **fixed** — Fixed handling of Date and Uint8Array values created in other JavaScript realms such as iframes jsdom and Node.js vm contexts
- **fixed** — Invalid Date values passed to $queryRaw or $executeRaw now throw PrismaClientValidationError instead of a generic error
- **fixed** — Fixed moduleFormat inference for the prisma-client generator in TypeScript projects using module node16 or nodenext
- **fixed** — Deserialized Bytes values now own standalone ArrayBuffers rather than exposing unrelated contents from Node.js's shared Buffer pool
- **fixed** — Fixed incorrect logging context in the remote executor including Accelerate-backed query execution
- **changed** — Result-extension compute callbacks now receive the current model name as a typed second argument

#### Prisma ORM 7.10.0

Prisma ORM 7.10.0 introduces a compatibility package for running Prisma 7 alongside newer Prisma versions, secures Prisma Studio's local server, and includes fixes across Prisma Client and the PostgreSQL, MariaDB, Neon, SQLite, and Prisma Postgres Serverless adapters.

##### Highlights

###### Run Prisma 7 alongside 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.

Once 7.10.0 is released, a side-by-side installation can use:

```sh
npm install --save-dev prisma@8 @prisma/prisma7@7.10.0
npm install @prisma/client@7.10.0
```

Use `prisma` for the directly installed Prisma 8 CLI and `prisma7` for Prisma 7:

```sh
npx prisma --version
npx prisma7 --version

npx prisma7 generate
npx prisma7 migrate dev
npx prisma7 db push
```

Prisma 7 now prefers version-specific configuration files, allowing its configuration to coexist with Prisma 8's `prisma.config.*` files:

```ts
// prisma7.config.ts
import { defineConfig } from '@prisma/prisma7/config'

export default defineConfig({
  schema: 'prisma/schema.prisma',
  migrations: {
    path: 'prisma/migrations',
  },
})
```

Without an explicit `--config` option, Prisma 7 searches for:

1. Root-level `prisma7.config.*` files.
2. `.config/prisma7.*` files.
3. Existing `prisma.config.*` files as a backwards-compatible fallback.

The supported extensions are `.js`, `.ts`, `.mjs`, `.cjs`, `.mts`, and `.cts`. An explicit config path always takes precedence:

```sh
npx prisma7 generate --config ./custom/prisma7.config.ts
```

New projects initialized by the Prisma 7 CLI use `prisma7.config.ts`. Existing projects containing only `prisma.config.*` continue to work without migration or additional warnings. If a `prisma7.config.*` file exists but cannot be loaded, Prisma reports the error rather than silently falling back to another configuration.

The `prisma7` identity is carried through CLI help, version output, shell completion, initialization, migration, database, and generation guidance. Stable Prisma concepts such as `schema.prisma`, Prisma Migrate, `@prisma/client`, and `PRISMA_*` environment variables remain unchanged.

Together, the separate executable and configuration namespace make it possible to operate Prisma 7 and Prisma 8 side by side without command or config-file collisions.

[#29949](https://github.com/prisma/prisma/pull/29949), [#29969](https://github.com/prisma/prisma/pull/29969), [#29994](https://github.com/prisma/prisma/pull/29994), [#30000](https://github.com/prisma/prisma/pull/30000), [#30002](https://github.com/prisma/prisma/pull/30002), [#30020](https://github.com/prisma/prisma/pull/30020)

###### Prisma Studio security hardening

Prisma Studio's local HTTP server now:

- Binds explicitly to `127.0.0.1` instead of all network interfaces.
- Rejects browser requests from origins other than the active `localhost` or `127.0.0.1` Studio URL.
- No longer returns wildcard CORS headers.
- Applies the same protections across Node.js, Bun, and Deno.

This prevents network clients or malicious websites from accessing Studio's database endpoints while Studio is running.

[#29890](https://github.com/prisma/prisma/pull/29890)

##### Prisma Client

- Fixed `P2002` errors from nested writes so `meta.modelName` identifies the model where the unique constraint violation occurred, including models using `@@map` and `@@schema`. [#29628](https://github.com/prisma/prisma/pull/29628)
- Fixed automatically batched `findUniqueOrThrow()` calls so every missing record rejects with `P2025`; later misses no longer resolve to `undefined`. [#29654](https://github.com/prisma/prisma/pull/29654)
- Parameter-chunked statements are now executed atomically in a transaction and rolled back if a later chunk fails. [#29771](https://github.com/prisma/prisma/pull/29771)
- Impr

_[Truncated at 4000 characters — full notes: https://github.com/prisma/prisma/releases/tag/7.10.0]_