Release status
Where Prisma ORM 8 stands today, what you get when you install it, and how to stay on Prisma ORM 7.
Prisma ORM 8 is a release candidate: you can install it and build with it today. Until the final release, some details of the API may still change, so code you write now may need small edits later. Each release candidate fixes bugs found in the previous one.
It needs Node.js 22.18 or newer on the 22 line, 24.11 or newer on the 24 line, or 26 or newer, and TypeScript 5.9 or newer. The npm that ships with each of those Node.js releases works, including npm 10 on Node.js 22.
Before you decide, read what is not available yet. Today that includes $extends, filtering inside JSON columns, atomic increment, most nested writes, transaction isolation levels, and the P2002-style error codes.
When the final release is expected
General availability is expected in October 2026.
Prisma ORM 7 is supported for 18 months after the final release
Prisma ORM 7 keeps receiving bug fixes and security updates for 18 months from the day Prisma ORM 8 reaches general availability. Its documentation stays at /orm/v7.
Prisma ORM 6 receives security patches until 19 November 2026
Prisma ORM 6 receives security patches, but no other updates, for 12 months after the release of Prisma ORM 7, a period that ends on 19 November 2026. Its documentation stays at /orm/v6.
What you get when you install today
Prisma ORM 8 is two packages: the command-line tool, and a library your app imports. There is one library per database; for PostgreSQL it is @prisma/orm-postgres.
bun add --dev prisma
bun add @prisma/orm-postgresFor MongoDB the library is @prisma/orm-mongo. Supported databases lists every database and its status.
@prisma/orm-postgres needs the temporal-polyfill package, which it declares as a peer dependency. npm, pnpm, and bun install it for you. With Yarn, add it to your dependencies yourself: yarn add temporal-polyfill.
The two packages have different version numbers, and that is normal: they are released separately, and the command-line tool gets more frequent releases. Install both at latest; any two latest versions work together, and you do not pair the numbers yourself.
| Package | latest on 16 October 2026 |
|---|---|
prisma (the command-line tool) | 8.0.0-rc.23 |
@prisma/orm-postgres (the library) | 8.0.0-rc.18 |
@prisma/orm-mongo (the MongoDB library) | 8.0.0-rc.18 |
To see the latest version of each package today, run npm view prisma dist-tags, npm view @prisma/orm-postgres dist-tags, and npm view @prisma/orm-mongo dist-tags, and read the latest entry in each result. You need all three commands because the command-line tool and the libraries are versioned separately.
@prisma/client, the library that Prisma ORM 7 apps import, stays at 7.10.1, because it belongs to Prisma ORM 7 and is not part of Prisma ORM 8.
npm install prisma and npx prisma now give you the Prisma ORM 8 command-line tool, which does not read schema.prisma and has no generate, migrate dev, or db push commands. If your project is on Prisma ORM 7, run npm install --save-dev prisma@7 now, and lock the version in package.json as shown below. If version 8 is already installed, that same command downgrades it. To see what you have now, run npm ls prisma @prisma/client.
How to stay on Prisma ORM 7
Lock both packages to version 7 in package.json:
{
"devDependencies": {
"prisma": "^7"
},
"dependencies": {
"@prisma/client": "^7"
}
}Anywhere you run the tool without a locked version, for example in CI or in a one-off command, write npx prisma@7 instead of npx prisma.
The Prisma ORM 7 documentation is at /orm/v7, its setup guides at /v7/getting-started, and its command reference at /cli/v7.
Next steps
- To move an existing Prisma ORM 7 app, follow Migrate from Prisma ORM 7 to 8. It runs both versions side by side and moves one part of the app at a time.
- To see what each Prisma ORM 7 command and query is called now, and what is not available yet, see Coming from Prisma ORM 7.
