$
npx @buildinternet/releases get prismaRecently Shipped21 releases · updated Aug 31, 2026
Prisma ORM v8.0.0-rc.8 landed this week alongside @prisma/prisma7, a compatibility package for running Prisma 7 and 8 in the same project.
Side-by-side Prisma 7 and 8 installation is now supported. 7.10.0 introduced @prisma/prisma7; install it with prisma@8 to keep a prisma7 alias for all Prisma 7 CLI commands while upgrading incrementally. 7.10.0 also secured Prisma Studio's local server against unauthorized access.
Prisma 8's RC series is accumulating breaking changes before GA. Projects preparing to migrate should note:
- Config:
prisma-next.config.tsand the flat config shape are removed (rc.4);prisma.config.tsusing thedefinePrismaConfigenvelope is the only accepted format. - Commands: ORM commands now mount at unified CLI paths —
db migrate,contract format,orm init— standalone aliases retired (rc.5). - Pagination:
.take(n)/.skip(n)on ORM collections renamed to.limit(n)/.offset(n)(rc.7). - Temporal: PostgreSQL date/time columns return
Temporalvalues or text strings, neverDate(rc.6). - Engine:
@prisma/management-api-sdkmoved to a peer dependency in rc.8; hosts running the engine outside the unified CLI must install it explicitly.
Earlier 7.x improvements remain active context. Query plan caching (tunable via queryPlanCacheMaxSize) shipped in 7.4.0–7.8.0. Nested transaction savepoints arrived in 7.5.0. prisma bootstrap unified hosted database setup in 7.7.0. Partial indexes are available as a preview feature for PostgreSQL, SQLite, SQL Server, and CockroachDB.
Raw SQL in a contract is now always a sql literal or value, a full-text index can span several weighted fields and is searched from the ORM by naming it, and middleware observes each statement and transaction as an activity. PSL gains mixins, the SQL ORM gains whereUnique…
Migrations no longer lose data without being told to: prisma migration plan and prisma db update ask about each model or field a plan would drop, answered with --delete or with the new --rename, which keeps the rows. The ORM client gains row locks, apply and scope…
In this release, connect() on the Postgres serverless client returns a connection with db.orm, db.transaction(...) and db.prepare(...), the same members as a postgres() client. A date or time default is stored in one canonical text for each value, so its storage hash…
This release brings MongoDB closer to Postgres: a Mongo schema can declare Int64, Decimal128, Binary, Json and Bson fields and automatic timestamps, and a Prisma 6 MongoDB project can use its existing schema.prisma as the contract source. The ORM client can order by…
This release adds Postgres full-text search, prepared ORM reads and aggregates, schemas split across several files, and a way for a Prisma 7 project to use its existing schema.prisma as the Prisma 8 contract source. It also changes how a schema is written: a model without…
This release moves the toolchain onto @prisma/cli-engine@0.4.0, which adds a Markdown output format to every CLI command. Nothing else changed since rc.10.
This RC finishes the rename from Prisma Next to Prisma 8 in every identifier a project can see (the old schema header keeps working, the old environment variables do not), adds named model and result types to the emitted contract, makes db sign set the db ref so the first…
This RC tightens schema validation, adds reusable query-filter types, and fixes language-server diagnostics and PostgreSQL migration verification.