NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #3157 most downloaded on npm
The Prisma CLI: one binary for the ORM, Composer, and the Prisma Developer Platform.
Latest stable
7.10.1
Last release 12 days ago
10 Nov 2026
Ships fairly regularly
a new release about every 8 days
Nearly every release is documented
notes for 58 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
10 years old
9416 releases · first in 2016
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Release 8.0.0-rc.33: follow the products' released versions: @prisma/composer-cli 0.37.0 -> 0.38.0; @prisma/composer 0.37.0 -> 0.38.0 by @prisma-bot i
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.32...v8.0.0-rc.33
TML-3439: A product release releases the CLI, so prisma@latest never pins an older ORM toolchain by @wmadden-electric in https://github.com/prisma/pri
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.31...v8.0.0-rc.32
docs: add the DEPLOY namespace to the error reference by @quicksilversel in https://github.com/prisma/prisma-cli/pull/377
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.30...v8.0.0-rc.31
Follow the products' released versions: @prisma/composer-cli 0.35.0 -> 0.36.0; @prisma/composer 0.35.0 -> 0.36.0 by @prisma-bot in https://github.com/
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.29...v8.0.0-rc.30
Follow the products' released versions: @prisma/orm-toolchain 8.0.0-rc.20 -> 8.0.0-rc.21 by @prisma-bot in https://github.com/prisma/prisma-cli/pull/3
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.28...v8.0.0-rc.29
Conformance drops the engine 0.7.0 exceptions: the ORM toolchain and Composer both peer engine 0.9.0 by @wmadden-electric in https://github.com/prisma
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.27...v8.0.0-rc.28
Follow the products' released versions: @prisma/composer-cli 0.33.0 -> 0.34.0; @prisma/composer 0.33.0 -> 0.34.0 by @prisma-bot in https://github.com/
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.26...v8.0.0-rc.27
Follow the products' released versions: @prisma/orm-toolchain 8.0.0-rc.19 -> 8.0.0-rc.20 by @prisma-bot in https://github.com/prisma/prisma-cli/pull/3
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.25...v8.0.0-rc.26
Follow the products' released versions: @prisma/orm-toolchain 8.0.0-rc.18 -> 8.0.0-rc.19 by @prisma-bot in https://github.com/prisma/prisma-cli/pull/3
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.24...v8.0.0-rc.25
feat(engine): a command can also have subcommands, so prisma dev and prisma dev url can coexist by @wmadden-electric in https://github.com/prisma/pris
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.23...v8.0.0-rc.24
fix: declare one supported Node.js range, ^22.18.0 || ^24.11.0 || >=26.0.0 by @wmadden-electric in https://github.com/prisma/prisma-cli/pull/343
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.22...v8.0.0-rc.23
feat(engine): commands can ask for a statement such as --delete Legacy, not only a copied confirmation token by @wmadden-electric in https://github.co
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.21...v8.0.0-rc.22
chore(cli): remove the engine 0.6.2 conformance exceptions by @wmadden-electric in https://github.com/prisma/prisma-cli/pull/328
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.20...v8.0.0-rc.21
fix(cli): make logout and update notices clearer by @AmanVarshney01 in https://github.com/prisma/prisma-cli/pull/317
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.19...v8.0.0-rc.20
Follow the products' released versions: @prisma/composer-cli 0.24.0 -> 0.25.0; @prisma/composer 0.24.0 -> 0.25.0 by @prisma-bot in https://github.com/
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.18...v8.0.0-rc.19
The engine 0.6.1 transition is over: delete the conformance exceptions by @wmadden-electric in https://github.com/prisma/prisma-cli/pull/291
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.17...v8.0.0-rc.18
docs: surface CLI feedback command by @gregory-boch-prisma in https://github.com/prisma/prisma-cli/pull/255
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.15...v8.0.0-rc.17
feat(engine): --format markdown, a third output format for agents by @wmadden-electric in https://github.com/prisma/prisma-cli/pull/260
--format markdown, a third output format for agents by @wmadden-electric in https://github.com/prisma/prisma-cli/pull/260Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.14...v8.0.0-rc.15
Rewrite CLI help as a self-documenting manual by @tylerhogarth in https://github.com/prisma/prisma-cli/pull/247
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.13...v8.0.0-rc.14
Follow the products' released versions: @prisma/composer-cli 0.16.0 -> 0.17.0; @prisma/composer 0.16.0 -> 0.17.0 by @StevenMcClankerton in https://git
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.12...v8.0.0-rc.13
Error-reference follow-ups: one code per condition, doc sync, legacy retirement by @wmadden-electric in https://github.com/prisma/prisma-cli/pull/238
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.11...v8.0.0-rc.12
Keep the next tag resolving instead of removing it by @wmadden-electric in https://github.com/prisma/prisma-cli/pull/231
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.10...v8.0.0-rc.11
Replace deprecated tsdown noExternal with deps.alwaysBundle by @wmadden-electric in https://github.com/prisma/prisma-cli/pull/223
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.9...v8.0.0-rc.10
Agent skills install from the npm packages the project already has by @wmadden-electric in https://github.com/prisma/prisma-cli/pull/219
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.8...v8.0.0-rc.9
Rework the command surface: explicit targeting, delete verbs, workflow-grouped commands by @wmadden-electric in https://github.com/prisma/prisma-cli/p
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.7...v8.0.0-rc.8
feat(compute): add future-compatible keep-awake control file path by @tensordreams in https://github.com/prisma/prisma-cli/pull/216
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.6...v8.0.0-rc.7
Sessions this CLI writes stay visible to the 3.x CLI sharing the store by @ankur-arch in https://github.com/prisma/prisma-cli/pull/212
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.5...v8.0.0-rc.6
Engine 0.2.0: the changed engine must ship, and CI now forces the bump by @wmadden-electric in https://github.com/prisma/prisma-cli/pull/200
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.4...v8.0.0-rc.5
The ORM command family now ships the unified CLI's command paths directly, the Postgres runtime survives dropped idle connections, aggregation respects the chain it terminates, and the raw lane lets an outer query reuse an inner query's typed return columns.
The upgrade recipe for this hop: the user recipe.
The ORM command family is keyed by the unified CLI's mount paths — @prisma/orm-toolchain's command family now publishes the six moved commands under their unified spellings (contract format, db migrate, migration ref list|set|delete, orm init) instead of the retired standalone grammar (format, migrate, ref …, init), and every help example and error remediation names those paths (with the {bin} placeholder instead of a hardcoded binary name). Through the unified prisma CLI nothing moves — these were already the mounted paths — but a host that mounts the family by key, or a script driving the workspace binary with the old spellings, must respell the six commands. (#30102)
Before:
prisma migrate --to production
prisma ref set staging 4cb4256
After:
prisma db migrate --to production
prisma migration ref set staging 4cb4256
.returns, a record of typed column refs, so an outer raw query can reuse an inner query's declared column (for example a CTE's aggregate) instead of restating its codec id. (#30075)aggregate() now reduces over exactly the rows a chain's take / skip / cursor / distinct / distinctOn describes, instead of silently reducing over every matching row. (#30067)groupBy() now scopes pre-group pagination to the rows it groups instead of dropping it, and GroupedCollection gained take / skip / orderBy to page the groups themselves. (#30092)'error' listeners to every pool and client it creates or receives, so a dropped idle connection (database restart, pooler timeout, network blip) no longer crashes the process as an uncaught exception. Pools your own code constructs and uses directly still need a listener — see the upgrade recipe. (#30081)orm init's failure messages no longer name retired flags or binaries (--no-skill, --force, prisma-cli init); they point at the flags that exist (--skip-skills, --confirm <directory name>) and the mounted prisma orm init. (#30083)Deploy a real service in e2e, and cover the eight commands that needed one by @wmadden-electric in https://github.com/prisma/prisma-cli/pull/178
Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.3...v8.0.0-rc.4
The transition period for the old ORM config is over, and two fixes land for the consolidated prisma CLI stack. Most projects created before rc.2 need the config migration below; projects scaffolded by rc.2+ init need nothing.
The upgrade recipe for this hop: the user recipe.
The deprecated config fallbacks are gone — the CLI no longer reads prisma-next.config.ts and no longer accepts the flat (un-nested) config shape; both now fail loudly instead of warning. The only config read is prisma.config.ts in the envelope shape, and the workspace prisma-next binary is retired — the unified CLI runs the ORM commands at the top level. Rename the file, wrap your ORM options in definePrismaConfig({ orm: ormConfig({ … }) }), and keep import 'dotenv/config' if your config reads process.env. See the user recipe for the exact rewrite. (#30058)
Before:
// prisma-next.config.ts
import { defineConfig } from '@prisma/orm-postgres/config';
export default defineConfig({ contract: './contract.prisma', db: { connection: process.env['DATABASE_URL']! } });
After:
// prisma.config.ts
import 'dotenv/config';
import { definePrismaConfig } from '@prisma/cli-engine';
import { defineConfig as ormConfig } from '@prisma/orm-postgres/config';
export default definePrismaConfig({
orm: ormConfig({ contract: './contract.prisma', db: { connection: process.env['DATABASE_URL']! } }),
});
contract emit no longer crashes after writing its artifacts when the project root is a relative path — validateContractDeps() resolves the root before handing it to Node's createRequire(), which requires an absolute path. (#30064)init scaffolds definePrismaConfig, the current name for the config marker in @prisma/cli-engine 0.2.0, instead of the deprecated defineConfig alias. (#30064)ADR 0004: one engine per install — the strategy, both handover briefs, and the engine decoupled from the lockstep by @wmadden-electric in https://gith
prisma, and this release is 8.0.0-rc.3 by @wmadden-electric in https://github.com/prisma/prisma-cli/pull/191Full Changelog: https://github.com/prisma/prisma-cli/compare/v8.0.0-rc.2...v8.0.0-rc.3
A single-purpose release: @prisma/orm-toolchain moves its exact @prisma/cli-engine peer from 0.1.1 to 0.2.0, so the unified prisma CLI can ship a release in which every mounted product runs on the one engine version it installs. There are no ORM API changes in this release.
@prisma/cli-engine peer moves to 0.2.0 — engine 0.2.0 adds the credential-refresh exports and structured delegated output that prisma@8.0.0-rc.4 was built against but the registry's engine 0.1.1 does not contain, which is why npx prisma@next currently fails on import. This release pairs with the prisma CLI release that depends on it (8.0.0-rc.5); upgrade both together. No code changes — an operational peer move only. (#30056)Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.