@prisma/client

Every stable release, newest first. Notes are quoted as the maintainers published them.

1. 7.10.0

   25 August 2026
   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

   Section of a shared release note

   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

   • Fixed automatically batched findUniqueOrThrow() calls so every missing record rejects with P2025; later misses no longer resolve to undefined. #29654

   • Parameter-chunked statements are now executed atomically in a transaction and rolled back if a later chunk fails. #29771

   • Improved interactive transaction cleanup during $disconnect(), including transactions whose driver-level startup is still in progress. #28768

   • Prevented transaction cleanup failures after a timeout or backend termination from becoming unhandled promise rejections. #29611

   • Fixed fluent relation queries when relation fields are literally named select or include. #29683

   • Fixed handling of Date and Uint8Array values created in other JavaScript realms, such as iframes, jsdom, and Node.js vm contexts. #29177

   • Invalid Date values passed to $queryRaw or $executeRaw now throw PrismaClientValidationError instead of a generic error. #29718

   • Fixed moduleFormat inference for the prisma-client generator in TypeScript projects using module: "node16" or "nodenext". Generated output now follows the nearest package.json type, defaulting to CommonJS when absent. #29712

   • Deserialized Bytes values now own standalone ArrayBuffers rather than exposing unrelated contents from Node.js's shared Buffer pool. This applies to both regular and raw query results. #29701

   • Fixed an incorrect logging context in the remote executor, including Accelerate-backed query execution. #28892

2. 7.9.1

   27 July 2026
   Today, we're issuing a patch release to resolve a security advisory in a transitive dependency of Prisma CLI (via @prisma/dev).

   Today, we're issuing a patch release to resolve a security advisory in a transitive dependency of Prisma CLI (via @prisma/dev).

   This fixes #29780.

   It does not actually affect @prisma/dev or Prisma CLI so no urgent action is required, but it is recommended to upgrade nevertheless to avoid false positives from security scanners.

3. 7.9.0

   20 July 2026
   Today, we are excited to share the 7.9.0 stable release 🎉

   Today, we are excited to share the 7.9.0 stable release 🎉

   🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

   Highlights

   ORM

   Tab completions for the Prisma CLI

   Typing out CLI commands from memory is now optional. Prisma ships shell tab completions for bash, zsh, fish, and PowerShell, covering commands, subcommands, options, flags, and even option values.

   Setting it up. Most projects run Prisma through a package manager, so completions are enabled through @bomb.sh/tab's package-manager integration — install it once, then source the completion for your package manager and shell:

   # 1. Install @bomb.sh/tab globally
   npm install -g @bomb.sh/tab
   
   # 2. Wire up your package manager + shell (pnpm shown; swap in npm / yarn / bun):
   echo 'source <(tab pnpm zsh)'  >> ~/.zshrc            # zsh
   echo 'source <(tab pnpm bash)' >> ~/.bashrc           # bash
   tab pnpm fish > ~/.config/fish/completions/pnpm.fish  # fish
   tab pnpm powershell > ~/.tab-pnpm.ps1                 # PowerShell (then dot-source it from $PROFILE)

   @bomb.sh/tab delegates to any locally-installed CLI that ships completions, so pnpm prisma <TAB>, pnpm exec prisma <TAB>, yarn prisma <TAB>, and bun x prisma <TAB> all complete Prisma's commands, options, and values — no per-project setup. (npx and bunx don't support completion themselves; use npm exec and bun x.)

   If instead you have Prisma installed globally on your PATH, source its own completion directly: source <(prisma complete zsh) (or the bash / fish / powershell variant).

   This is built on @bomb.sh/tab, the same completion library that powers other CLIs in the ecosystem — including Cloudflare, Nuxt, and Vitest — so the package-manager completions you enable for Prisma work for those tools too. A wonderful community contribution from @AmirSa12 (#28351) — thank you!

   github.com/user-attachments/assets/1f916a60-ee4…

   Prisma ORM, ready for AI agents

   Coding agents are now a first-class audience for Prisma, and 7.9.0 brings the first wave of work to make Prisma projects safe and productive for them to work in.

   Agent skills installed with prisma init

   prisma init now installs the prisma/skills catalog into freshly scaffolded projects. Agents such as Claude Code, Cursor, Codex, and Windsurf start out with current, version-relevant Prisma knowledge instead of relying on whatever happened to be in their training data. The install is best-effort and never blocks scaffolding; opt out at any time with --no-skills.

   npx prisma@latest init

   prisma init scaffolds a project and installs the Prisma agent skills catalog

   A safer default around destructive commands (#29684, #29691, #29713)

   Prisma's AI safety checkpoint refuses to run destructive commands when it detects that an AI agent is at the keyboard, unless the user has given explicit consent. In this release we:

   • Broadened agent detection to cover today's landscape — Codex CLI (now on Linux as well as macOS), Qwen Code, GitHub Copilot CLI, OpenCode, Cline, Goose, Amp, Crush, Augment Code, Antigravity, Replit Agent, and Devin — plus generic AI_AGENT / AGENT conventions so future agents are caught without a code change.

   • Extended the guard to db push --accept-data-loss, which previously bypassed the checkpoint even though it can drop data.

   • Removed the migrate-reset tool from the prisma mcp server entirely — resetting a database drops it, and that is not an operation an agent should be handed as a first-class tool. An agent that needs a reset must run the CLI, where the checkpoint applies.

   Bug Fixes

   Many of the fixes below are community contributions — thank you to everyone who reported and fixed these!

   Prisma Client

   • Fixed a severe TypeScript performance regression introduced in Prisma 7: restoring the OmitOpts generic default lets tsc reuse cached type instantiations again, bringing type-checking on large schemas back from minutes to seconds (#29592, from @nfl1ryxditimo12).

   • The XOR type helper now rejects primitive values such as data: 5, which were previously accepted at compile time even though the runtime rejected them (#29735, from @kyungseopk1m).

   • $queryRaw and $executeRaw now fail fast with a clear validation error when passed an invalid Date, instead of silently serializing it as null and corrupting the value sent to the database (#29697, from @jibin7jose).

   • The generated client is no longer corrupted by a /// documentation comment that contains a */ sequence; the comment terminator is now escaped when doc comments are emitted, in both the TypeScript and JavaScript generators (#29736, from @kyungseopk1m).

Major versions

• 7.xsince 19 November 2025 · latest 7.10.0 · 15 releases
• 6.xsince 28 November 2024 · latest 6.19.3 · 35 releases
• 5.xsince 11 July 2023 · latest 5.22.0 · 40 releases
• 4.xsince 28 June 2022 · latest 4.16.2 · 27 releases
• 3.xsince 7 September 2021 · latest 3.15.2 · 27 releases
• 2.xsince 9 June 2020 · latest 2.30.3 · 57 releases