Change8

Prisma

Backend & Infra

Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB

Latest: v8.0.0-rc.825 releases13 breaking changes13 common errorsView on GitHub

Release History

View all versions →
v8.0.0-rc.8Breaking4 fixes1 feature
Aug 26, 2026

This release updates the toolchain to use `@prisma/cli-engine@0.3.0` and refines the `migration plan` command to prevent silent failures from empty databases when migrations exist. It also improves language server compatibility with Windows paths.

7.10.018 fixes4 features
Aug 25, 2026

Prisma ORM 7.10.0 enhances compatibility by introducing a package to run Prisma 7 alongside Prisma 8 and improves Prisma Studio's local server security. It also includes numerous bug fixes across Prisma Client and various database adapters.

v8.0.0-rc.7Breaking1 fix
Aug 25, 2026

This release renames ORM pagination methods from `take`/`skip` to `limit`/`offset` and updates the engine peer dependency to `@prisma/cli-engine@0.2.3`.

v8.0.0-rc.6Breaking2 fixes2 features
Aug 25, 2026

This release updates PostgreSQL temporal column handling to explicit Temporal or text representations and integrates the prisma-8 agent skill directly into ORM packages. It also refactors agent skill setup to the family-level `prisma init` command and updates the CLI engine for improved pnpm compatibility.

v8.0.0-rc.5Breaking6 fixes1 feature
Aug 22, 2026

This release rekeys the ORM command family by unified CLI mount paths and improves the robustness of the Postgres runtime against dropped connections. It also enhances raw query capabilities and fixes several issues with aggregation, pagination, and CLI error reporting.

v8.0.0-rc.4Breaking2 fixes
Aug 18, 2026

The transition period for the old ORM config is over, and two fixes land for the consolidated `prisma` CLI stack. Most projects require a config migration to the new `prisma.config.ts` format.

v8.0.0-rc.3Breaking
Aug 18, 2026

This release unifies the `@prisma/cli-engine` peer dependency to 0.2.0, ensuring all mounted products use the installed engine version. There are no ORM API changes.

v8.0.0-rc.2-dev.15 fixes2 features
Aug 17, 2026

This release updates development dependencies, including Biome, Turbo, and Prisma SDKs. It also introduces new Biome rules for React Compiler and Svelte, alongside several bug fixes and performance improvements.

v8.0.0-rc.2Breaking3 fixes3 features
Aug 17, 2026

This release bumps the version to 8.0.0-rc.2, adopting `@prisma/cli-engine` 0.1.1 which introduces breaking changes in runtime host information and CI detection. It also includes fixes for the dev build counter and CLI output handling.

v8.0.0-rc.1-dev.46Breaking2 fixes2 features
Aug 17, 2026

The CLI engine is now an exact peer dependency of the toolchain, preventing version conflicts and improving installation reliability. Conformance checks have been updated to support bin-less packages and detect incorrect dependency placements.

v8.0.0-rc.1-dev.456 features
Aug 13, 2026

The affected-row-counts project is now complete, with count-returning writes using a single statement and returning database-reported statistics. Documentation has been updated to reflect current behavior and supported operations.

v8.0.0-rc.1-dev.443 features
Aug 13, 2026

The minimum supported PostgreSQL version for Prisma 8 has been lowered to 15, impacting project initialization and database probing. This change aligns the declared floor with existing CI practices and broadens compatibility for users on PostgreSQL 15 and 16.

v8.0.0-rc.1-dev.433 features
Aug 13, 2026

Introduced automated conformance checks to the publishing workflow to ensure package integrity, import purity, validator robustness, and clean tarball installations. These checks enhance the quality and reliability of published packages.

v8.0.0-rc.1-dev.42Breaking4 features
Aug 12, 2026

This release refactors write operations to return affected row counts directly from the write statement, eliminating an extra round trip and race condition. It also introduces explicit separation between row retrieval (`query()`) and statistics (`execute()`) operations.

v8.0.0-rc.1-dev.411 fix
Aug 12, 2026

Added documentation for the MIGRATION.CONSENT_PLAN_MISMATCH error, resolving linting issues. This change clarifies that migrations are rejected if the apply-time plan differs from the approved plan.

v8.0.0-rc.1-dev.40Breaking5 fixes8 features
Aug 12, 2026

The `db verify`, `db sign`, and `migration check` commands now provide more granular exit codes to distinguish between findings (exit 4) and execution errors (exit 2). Internal CLI bugs are now consistently reported with exit code 1.

v8.0.0-rc.1-dev.39Breaking4 features
Aug 12, 2026

The `migration plan`, `migration new`, and `migration status` commands have been migrated to the new engine-based CLI. Retired `migration status` flags are now redirects to their new locations.

v8.0.0-rc.1Breaking4 fixes1 feature
Aug 7, 2026

This release introduces the v8 release-candidate line, versioned as `8.0.0-rc.N`, and changes how aggregate results are read back through codecs, impacting types like `count()` which now returns `bigint`. It also splits the SQL driver interface and fixes several defects in query planning, emit, and driver error reporting.

v0.17.0Breaking2 fixes3 features
Aug 4, 2026

This release introduces a namespace change, publishing Prisma Next as 17 packages under the `@prisma` scope. It also standardizes error handling with structured envelopes and completes relation-loading for lossless data handling.

7.9.11 fix
Jul 27, 2026

A patch release addresses a security advisory in a transitive dependency of Prisma CLI. While no direct impact is expected, upgrading is recommended to prevent false positives from security scanners.

7.9.0
Jul 21, 2026
7.8.09 fixes1 feature
Apr 22, 2026

The 7.8.0 release introduces fine-grained control over the query plan cache via `queryPlanCacheMaxSize` in `PrismaClient` and resolves numerous bugs across PostgreSQL, SQL Server, and migration tooling.

7.7.03 features
Apr 7, 2026

The 7.7.0 release introduces the highly requested `prisma bootstrap` command for streamlined Postgres setup and configuration. It also highlights enterprise support options and open roles at Prisma.

6.19.31 fix
Apr 1, 2026

Prisma 6.19.3 is a patch release primarily focused on updating the internal `effect` dependency to address a security vulnerability.

7.6.07 fixes9 features
Mar 27, 2026

The 7.6.0 release introduces significant enhancements to Prisma Studio, including Dark Mode, multi-cell editing, and AI-powered SQL generation. It also brings new CLI commands and improved driver adapter ergonomics and stability.

Common Errors

PrismaClientKnownRequestError12 reports

PrismaClientKnownRequestError usually indicates a problem stemming from the Prisma Client attempting an operation that violates a database constraint (like a unique constraint), or experiencing an issue with connection parameters. Fix it by carefully examining the `code` property of the error object to identify the specific issue (e.g., P2002 for unique constraint violations) and adjust your Prisma Client code and database schema/connection URL accordingly, or upgrading to the latest prisma version for bug fixes. Also ensure your database connection string includes all necessary parameters, such as the schema if relevant.

DriverAdapterError8 reports

DriverAdapterError in Prisma usually indicates a mismatch or misconfiguration between the Prisma client and the underlying database driver. Ensure your database connection string in the Prisma schema is correct, the database server is running and accessible, and that the Prisma client and adapter versions are compatible with your database version. Double-check for typos in the connection string and verify that the necessary database driver dependencies (e.g., `pg`, `mysql2`) are installed.

PrismaClientInitializationError5 reports

PrismaClientInitializationError usually stems from connection issues to your database or misconfiguration, often due to an incorrect or missing DATABASE_URL environment variable. To fix it, ensure your DATABASE_URL is correctly set in your environment and that your database server is running and accessible from your application. Double-check your Prisma schema for accuracy and consider using `npx prisma migrate dev` to ensure schema and database are in sync.

PrismaClientRustPanicError5 reports
PrismaClientValidationError3 reports

The "PrismaClientValidationError", especially around enums, often arises from mismatches between the Prisma schema's enum definitions and the data you're trying to insert (e.g., using a mapped value instead of the actual database value or providing an invalid enum value). Ensure the values passed to Prisma Client for enum fields exactly match the enum values defined in your Prisma schema and reflect the underlying database values if `@map` is not correctly configured. If using `@map`, verify Prisma's generated code correctly interprets the mapping during data creation/updates, potentially requiring schema adjustments or Prisma upgrade.

PrismaClientConstructorValidationError3 reports

The "PrismaClientConstructorValidationError" often arises from incorrect Prisma Client initialization, especially after version upgrades. Verify that your Prisma Client constructor includes either the `adapter` option for adapter-based setups or the `accelerateUrl` option when using Prisma Accelerate, as required by your Prisma version, or for older versions, missing specific engine types altogether. Ensure the specified `engineType` in your schema and constructor options (like `client` or `binary`) is compatible and correctly configured in your `PrismaClient` constructor.

Related Backend & Infra Packages

Subscribe to Updates

Get notified when new versions are released

RSS Feed