This release introduces significant changes including Postgres full-text search, prepared ORM reads, and schema file splitting. It also includes several breaking changes requiring careful migration.
affected
Projects using Prisma ORM, especially those with custom configurations or relying on `dbgenerated` defaults, are affected by these changes.
action
Follow the provided upgrade recipes for detailed migration steps.
release_signals
-Engine peer moves to `@prisma/cli-engine@0.6.1`, requiring `definePrismaConfig` instead of `defineConfig`.
-PSL models without `@@map` now name their tables exactly as written, requiring explicit `@@map` for previous behavior.
-Every PSL schema file must start with `// use prisma-8` to be included in the contract.
-`dbgenerated(...)` is removed; raw SQL defaults must use `sql` tagged literals.
-Column defaults must now be values that the column's data type accepts.
!`.defaultSql('...')` in TypeScript contract builder is deprecated in favor of `.default(now())`, `.default(autoincrement())`, or ``.default(sql`...`)``.
+Postgres full-text search support.
+Prepared ORM reads and aggregates.
+
migration_steps5 steps
01Update `@prisma/cli-engine` to version 0.6.1 and replace `defineConfig` with `definePrismaConfig`.
02Run the `add-model-map` script to add `@@map` to models without it.
03Add `// use prisma-8` to the first line of every PSL schema file.
04Replace `dbgenerated(...)` with `sql` tagged literals or appropriate functions like `now()`.
05Ensure column defaults match the column's data type.
This release updates the toolchain to `@prisma/cli-engine@0.4.0`, introducing Markdown output format for CLI commands. No other changes were made since rc.10.
affected
Projects pinning `@prisma/cli-engine` must update their pin to `0.4.0`.
action
Update the engine pin to `@prisma/cli-engine@0.4.0` if your project pins it directly.
release_signals
-The engine peer dependency has been updated to `@prisma/cli-engine@0.4.0`. Projects pinning the engine must update their pin to `0.4.0`.
+Added Markdown output format (`--format markdown`) to every CLI command.
This release completes the rename from Prisma Next to Prisma 8, introduces named model and result types, and adds attribute completion to the language server. It includes breaking changes for environment variables and contract types.
affected
Users relying on `PRISMA_NEXT_*` environment variables or needing to update contract types for to-one relations are affected.
action
Update environment variables and run `prisma contract emit` to ensure compatibility with the new contract format.
release_signals
-CLI environment variables lose the `NEXT_` infix. Rename `PRISMA_NEXT_*` to `PRISMA_*` in shell profiles, `.env` files, and CI.
This release candidate introduces stricter schema validation, reusable query-filter types, and fixes for language-server diagnostics and PostgreSQL migration verification. It includes several breaking changes, particularly around MongoDB schema handling and SQL ORM filter types.
affected
Developers using PostgreSQL enums, MongoDB schemas, or SQL ORM filter types are affected by the breaking changes and need to update their schemas and code accordingly.
action
Review and apply the provided upgrade recipes to migrate schemas and code to be compatible with this release.
release_signals
-Text-backed enum ordering in PostgreSQL now follows stored values, requiring explicit ranking expressions or numeric enum values for semantic ranking.
This release introduces breaking changes to the engine peer dependency and improves the migration system. It also includes several fixes related to migration planning, structured errors, and language server behavior.
affected
Users relying on the engine peer dependency or migration planning from an empty database are affected.
action
Upgrade to v8.0.0-rc.8 and follow the provided migration steps if necessary.
release_signals
-The engine peer dependency moves to `@prisma/cli-engine@0.3.0`, requiring `@prisma/management-api-sdk` as a peer dependency. Hosts pinning the engine must upgrade and install the SDK if running outside the CLI shell.
This release introduces breaking changes to ORM pagination, renaming `take`/`skip` to `limit`/`offset`. It also updates the engine peer dependency to `@prisma/cli-engine@0.2.3`.
affected
Users relying on `.take(n)` and `.skip(n)` for ORM pagination or manually pinning the engine peer dependency are affected.
action
Update ORM queries to use `.limit(n)` and `.offset(n)` and ensure the engine peer dependency is set to `@prisma/cli-engine@0.2.3`.
release_signals
-ORM pagination methods `.take(n)` and `.skip(n)` are renamed to `.limit(n)` and `.offset(n)` for SQL and Mongo ORM collections. The old names are removed, but semantics remain unchanged.
-The engine peer dependency is updated to `@prisma/cli-engine@0.2.3`. Hosts pinning the engine must upgrade to this version.
This release introduces breaking changes for PostgreSQL temporal columns and agent skills setup, while adding the prisma-8 skill to npm tarballs.
affected
Users of PostgreSQL temporal columns and those relying on `prisma orm init` for agent skills setup are affected.
action
Follow the migration recipe for PostgreSQL temporal columns and update to `@prisma/cli-engine@0.2.2`.
release_signals
-PostgreSQL temporal columns now use explicit `Temporal` or text representations instead of `Date`. Users must choose a representation per column and re-emit contracts.
This release introduces breaking changes to ORM command paths, adds typed column references for raw queries, and fixes several aggregation and Postgres connection handling issues.
affected
Users who directly invoke ORM commands or script them with old spellings are affected by the breaking CLI path changes.
action
Update command invocations to use the new unified CLI paths and follow the provided upgrade recipe.
release_signals
-The ORM command family is keyed by the unified CLI's mount paths. Commands like `prisma migrate` must now be respelled as `prisma db migrate` or `prisma migration ref set`.
This release finalizes the transition from the old ORM config to the consolidated `prisma` CLI stack. Projects created before rc.2 require a config migration, while those scaffolded by rc.2+ `init` are unaffected. Two fixes address issues with `contract emit` and `init` scaffolding.
affected
Projects created before rc.2 are affected and require a config migration.
action
Follow the [user recipe](https://github.com/prisma/prisma/tree/v8.0.0-rc.4/skills/prisma-next-upgrade/upgrades/8.0.0-rc.3-to-8.0.0-rc.4/) for the exact migration steps.
release_signals
-The deprecated config fallbacks are removed. The CLI no longer reads `prisma-next.config.ts` or accepts the flat config shape. The unified CLI now runs ORM commands at the top level, and the `prisma-next` binary is retired. Users must rename their config file and wrap ORM options in `definePrismaConfig`.
v8.0.0-rc.3mediumbreakingprereleaseAug 18, 2026
v8.0.0-rc.3
This release focuses on updating the `@prisma/orm-toolchain` to use `@prisma/cli-engine` version 0.2.0, ensuring compatibility with the unified `prisma` CLI. No ORM API changes are included.
affected
Users relying on `@prisma/orm-toolchain` and `prisma` CLI must upgrade both components together to avoid import failures.
action
Upgrade `@prisma/orm-toolchain` and `prisma` CLI to compatible versions (`8.0.0-rc.3` and `8.0.0-rc.5` respectively).
release_signals
-The exact `@prisma/cli-engine` peer dependency moves to 0.2.0 to support credential-refresh exports and structured delegated output, required for `prisma@8.0.0-rc.4` compatibility. Upgrade both `@prisma/orm-toolchain` and `prisma` CLI together.
This release introduces significant changes, including retiring the `prisma-next` binary in favor of the unified `prisma` CLI, reverting default aggregates to plain JavaScript numbers, and making CHECK constraints a declared part of the contract. Almost every application will need to re-emit its contract and rename its config file.
affected
Almost every application using Prisma will need to re-emit its contract and rename its config file.
action
Follow the provided upgrade recipes to migrate to the new version.
release_signals
-The `prisma-next` binary is retired; use the unified `prisma` CLI
This release candidate introduces breaking changes to aggregate result types and the SQL driver interface, while simplifying skill installation. It also fixes several query planning and emit defects.
affected
Users relying on aggregate results (e.g., `count()`) or custom SQL driver implementations are affected.
action
Review breaking changes and update code accordingly, especially for aggregate operations and custom SQL drivers.
release_signals
-Aggregate results now carry the codec their target declares, changing application types (e.g., `count()` returns a `bigint` instead of a number).
This release introduces significant changes to Prisma's package structure, error handling, and database facade dependencies. It also enhances relation-loading, SQL index naming, and migration contract storage.
affected
This release affects all Prisma users due to significant package restructuring and error handling changes.
action
Follow the 0.16-to-0.17 upgrade recipe to migrate your application.
release_signals
-Applications now depend on one `@prisma` package (e.g., `@prisma/orm-postgres`) instead of multiple `@prisma-next/*` packages.
-All errors are now structured envelopes with dotted codes, replacing legacy error systems.
7.9.0highbreakingfeatureJul 21, 2026
7.9.0
This release introduces shell tab completions for the Prisma CLI across multiple shells and enhances AI agent safety by preventing destructive commands without explicit consent. It also includes several bug fixes and improvements to Prisma Client and CLI.
affected
Developers using Prisma CLI and AI agents integrating with Prisma are affected.
action
Update to Prisma 7.9.0 to benefit from new features and improvements.
release_signals
-Removed `migrate-reset` tool from `prisma mcp` server to prevent AI agents from executing destructive operations.
+Shell tab completions for Prisma CLI in bash, zsh, fish, and PowerShell.
+AI agent safety checkpoint to prevent destructive commands without explicit consent.
Schemas can now be split across several files.
+Prisma 7 projects can use their existing `schema.prisma` as the Prisma 8 contract source.
migration_steps2 steps
01Follow the [app recipe](https://github.com/prisma/orm/blob/v8.0.0-rc.11/skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.10-to-8.0.0-rc.11/) for upgrading applications.
02Follow the [extension recipe](https://github.com/prisma/orm/blob/v8.0.0-rc.11/skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.10-to-8.0.0-rc.11/) for upgrading extensions.
To-one relations record their nullability in the contract. Run `prisma contract emit` once after upgrading to update `contract.d.ts` with the new `Models` namespace.
!The schema header `// use prisma-next` is deprecated in favor of `// use prisma-8`. The old header still works but will be rewritten to the new form when formatting the file.
+Named model and result types in `contract.d.ts` with `Models` namespace and `models` constant.
+Attribute completion in the language server for field, model, and block attributes.
+`db sign` can choose or skip the ref it advances with `--advance-ref` and `--no-advance-ref` options.
migration_steps2 steps
01Rename `PRISMA_NEXT_*` environment variables to `PRISMA_*`.
02Run `prisma contract emit` to update `contract.d.ts` with the new `Models` namespace.
The `prisma-8` skill now teaches agents the migration system's real model, preventing full-create plans against real databases.
migration_steps1 steps
01Follow the [user recipe](https://github.com/prisma/prisma/tree/v8.0.0-rc.8/skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.7-to-8.0.0-rc.8/) for upgrading from v8.0.0-rc.7 to v8.0.0-rc.8.
`prisma orm init` no longer installs agent skills; this functionality is moved to the family-level `prisma init` command.
-The engine peer dependency has been updated to `@prisma/cli-engine@0.2.2`, which includes fixes for pnpm symlink layouts and CI detection.
+The prisma-8 skill is now included in npm tarballs (`@prisma/orm-postgres`, `@prisma/orm-sqlite`, `@prisma/orm-mongo`), allowing `prisma skills sync` to detect staleness from installed packages.
migration_steps3 steps
01Choose a representation (`Temporal` or text) for each PostgreSQL temporal column and re-emit contracts.
02Update to `@prisma/cli-engine@0.2.2` if manually pinned.
03Use `prisma init` instead of `prisma orm init` for agent skills setup.