# Prisma ORM 6 Support Ends 19 November 2026: What to Do Now

Prisma ORM 6 stops receiving security patches on 19 November 2026. Here is what the official release-status page says, who is affected, and a short checklist for moving to ORM 7.

By Waseem Anjum · Published 2026-11-11 · Updated 2026-11-13 · https://fabwaseem.com/blog/prisma-6-end-of-support-november-2026

> **TL;DR:** Per Prisma's release-status page, ORM 6 gets security patches only, and that ends on 19 November 2026. ORM 7 keeps bug and security fixes for 18 months after ORM 8 reaches GA. ORM 8 is still a release candidate. Plan the move to ORM 7 now.

If you still run Prisma ORM 6, there is a date to put in your calendar: 19 November 2026. After that, the official support policy says ORM 6 no longer gets even security patches. The checklist below follows Prisma's official release-status page and changelog; check each step against your own schema.

## What does the Prisma support policy say?

The [release-status page](https://www.prisma.io/docs/orm/release-status) sets out three tracks. On 11 November 2026 it listed `latest` versions dated 6 November 2026.

| Version | Policy on the page |
| --- | --- |
| ORM 6 | Security patches, but no other updates, for 12 months after the release of ORM 7. End date: 19 November 2026. |
| ORM 7 | Bug fixes and security updates for 18 months from the day ORM 8 reaches general availability. |
| ORM 8 | Release candidate. The page said GA is expected in October 2026. |

![Three cards comparing Prisma ORM 6, 7 and 8 support: ORM 6 security patches only until 19 Nov 2026, ORM 7 bug fixes and security for 18 months after ORM 8 GA, ORM 8 release candidate](https://res.cloudinary.com/wasicloudinary/image/upload/v1794370102/fabwaseem/projects/iqmm6dbx2pc3d77gfuoq.jpg)

ORM 7 shipped as v7.0.0 on 19 November 2025 according to the [Prisma changelog](https://www.prisma.io/changelog), which matches the 12-month window ending on the same day a year later.

## Which versions are current right now?

The page lists these `latest` versions as of 6 November 2026:

| Package | Version |
| --- | --- |
| `prisma` (CLI) | 8.0.0-rc.33 |
| `@prisma/orm-postgres` | 8.0.0-rc.23 |
| `@prisma/orm-mongo` | 8.0.0-rc.23 |
| `@prisma/client` (stays on ORM 7) | 7.10.1 |

Note the split: the CLI and the libraries are versioned and released separately, and the page says to install both at `latest`. That is why the CLI can be on an 8.0.0 release candidate while the client is on 7.10.1.

## Is ORM 8 out yet?

Prisma's release-status page still lists ORM 8 as a release candidate, with GA expected in October 2026. Release candidate numbers may have moved since the page was last updated, so check the changelog or run `npm view prisma dist-tags` before you decide.

The changelog describes what ORM 8 is aiming at. Entries from the last few months mention that it works with an existing Prisma 7 schema (2 October), asks before dropping models or fields in migrations (9 October), and returns dates as JavaScript `Date` values (30 October). Those are release-candidate notes, so details may still change.

If you want background on the new generation, I covered it in [Prisma 8: what changes](https://fabwaseem.com/blog/prisma-8).

## What should you do before 19 November?

For most teams the pragmatic target is ORM 7, not a release candidate. It is the stable line, and its support clock runs until 18 months after ORM 8 GA.

![Four-step checklist for moving off Prisma 6: check Node runtime, check TypeScript version, upgrade prisma and client, then test migrations and tests](https://res.cloudinary.com/wasicloudinary/image/upload/v1794370110/fabwaseem/projects/yvml23w3oc2li6gueu4q.jpg)

1. **Check your runtime.** The page lists Node.js 22.18+, 24.11+ or 26+. If you are on an older Node, that comes first. My [Node 24 vs Node 26](https://fabwaseem.com/blog/node-24-vs-node-26) comparison helps pick one.
2. **Check TypeScript.** The page lists TypeScript 5.9+.
3. **Upgrade both packages together.** Install `prisma` and `@prisma/client` at the same ORM 7 version.
4. **Test.** Run your migrations against a staging copy of the database and your full test suite before touching production.

```bash
npm install prisma@7 @prisma/client@7
npx prisma generate
```

Read the official upgrade guide for breaking changes between 6 and 7 first.

## Does anything stop working on the day?

Nothing in the source says installed ORM 6 versions stop running. The change is about maintenance: a new vulnerability found after 19 November would not get a patch in the 6 line. For an API that handles user data, that matters. If you build backends on Prisma, my [secure NestJS and Prisma API starter](https://fabwaseem.com/blog/secure-nestjs-prisma-api-starter) shows the kind of setup that benefits from staying on supported releases.

If you are weighing alternatives, [Drizzle vs Prisma](https://fabwaseem.com/blog/drizzle-vs-prisma) covers the tradeoffs.

## Key takeaways

- ORM 6 gets security patches only, and the official end date is 19 November 2026.
- ORM 7 is supported for 18 months after ORM 8 reaches GA.
- ORM 8 is still listed as a release candidate, with no GA announcement yet.
- Requirements: Node.js 22.18+, 24.11+ or 26+, and TypeScript 5.9+.
- Upgrade to ORM 7 in staging first, and verify against the official docs.

Sources: [Prisma release status](https://www.prisma.io/docs/orm/release-status) and the [Prisma changelog](https://www.prisma.io/changelog).

## Questions

### When does Prisma ORM 6 support end?

According to Prisma's release-status page, ORM 6 receives security patches but no other updates for 12 months after ORM 7 was released. The page gives the end date as 19 November 2026.

### Should I upgrade to Prisma ORM 7 or wait for ORM 8?

ORM 8 is still listed as a release candidate, so ORM 7 is the stable target. ORM 7 keeps getting bug fixes and security updates for 18 months after ORM 8 reaches general availability.

### What Node.js and TypeScript versions does current Prisma need?

The release-status page lists Node.js 22.18+, 24.11+ or 26+, and TypeScript 5.9 or newer.

### Will my app stop working on 19 November?

Nothing in the source says existing installs stop running. It says ORM 6 stops getting security patches, so any new vulnerability would go unfixed in that line.