{"id":"src_Dl0-sZ84Cltb3e0ouROc7","slug":"prisma","name":"Prisma","type":"github","url":"https://github.com/prisma/prisma","orgId":"org_6F6EsC0Cws6EYvP51WlLX","productId":null,"productSlug":null,"org":{"id":"org_6F6EsC0Cws6EYvP51WlLX","slug":"prisma","name":"Prisma"},"isPrimary":false,"isHidden":false,"discovery":"curated","fetchPriority":"normal","metadata":"{\"changelogDetectedAt\":\"2026-03-31T14:07:53.424Z\",\"wellKnownSweptAt\":\"2026-10-31T06:00:36.365Z\"}","notice":null,"kind":"sdk","stars":47658,"starsFetchedAt":"2026-11-06T20:35:12.528Z","releaseCount":293,"releasesLast30Days":1,"avgReleasesPerWeek":0.2,"latestVersion":"7.10.1","latestDate":"2026-10-19T08:13:27.000Z","changelogUrl":null,"hasChangelogFile":true,"lastFetchedAt":"2026-11-06T20:35:12.528Z","lastPolledAt":"2026-11-06T20:34:54.335Z","changeDetectedAt":null,"trackingSince":"2020-06-09T08:19:35.000Z","releases":[{"id":"rel_Ur2CXGz6XqQ-NYUFFg-W_","version":"7.10.1","type":"feature","title":"7.10.1","summary":"Prisma ORM 7.10.1 is a patch release. It fixes a bug where a nested interactive transaction could make later, unrelated transactions run inside the wrong transaction. It also updates dependencies that had security advisories.","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"Prisma ORM 7.10.1 is a patch release. It fixes a bug where a nested interactive transaction could make later, unrelated transactions run inside the wrong transaction. It also updates dependencies that had security advisories.\n\n## Fixes\n\n### Prisma Client: nested `$transaction` no longer changes the options object you pass in\n\nIf you passed the same options object to a nested `tx.$transaction(...)` and later to a top-level `prisma.$transaction(...)`, the nested call wrote the outer transaction's id into that object. Every later top-level transaction that used the object was then treated as nested inside that old transaction:\n\n- if the old transaction had committed, the new one failed with `P2028`;\n- if the old transaction was still open, the new one silently ran as a savepoint inside another request's transaction.\n\n```ts\nconst TX_OPTIONS = { timeout: 30_000, maxWait: 10_000 }\n\nawait prisma.$transaction(async (tx) => {\n  await tx.$transaction(async (inner) => { /* ... */ }, TX_OPTIONS)\n})\n\n// Before 7.10.1, this call could fail with P2028 or join another transaction.\nawait prisma.$transaction(async (tx) => { /* ... */ }, TX_OPTIONS)\n```\n\nPrisma Client no longer modifies the options object. (https://github.com/prisma/orm/pull/30368, thanks @lazerg)\n\n### Prisma Migrate: refuse a shadow database that is the main database\n\nPrisma Migrate now refuses to run with error `P3025` when the shadow database URL points at the same database as the main database URL. Before, `prisma migrate diff --from-migrations` with that setup dropped the real schema, rebuilt it from the migrations, and reported an empty diff. (https://github.com/prisma/prisma-engines/pull/5851)\n\n### MariaDB adapter: updated to `mariadb` 3.5.4\n\n`@prisma/adapter-mariadb` now depends on `mariadb` 3.5.4, which fixes several security advisories in 3.5.3. The adapter no longer rewrites IPv6 hosts in connection strings, because `mariadb` 3.5.4 accepts them as written. IPv6 connection strings keep working without changes. (https://github.com/prisma/orm/pull/30668)\n\n## Dependency updates\n\nDependencies with security advisories were updated: `mysql2`, `fast-uri`, `deepmerge-ts`, `mariadb` and `source-map-js`. (https://github.com/prisma/orm/pull/30314, https://github.com/prisma/orm/pull/30189, https://github.com/prisma/orm/pull/30668)\n","publishedAt":"2026-10-19T08:13:27.000Z","fetchedAt":"2026-10-19T11:48:33.962Z","url":"https://github.com/prisma/orm/releases/tag/7.10.1","media":[],"coverageCount":0},{"id":"rel_pvz7AgkcGUo5OhiJo7eGd","version":"7.10.0","type":"feature","title":"7.10.0","summary":"Prisma ORM 7.10.0 Prisma ORM 7.10.0 introduces a compatibility package for running Prisma 7 alongside newer Prisma versions, secures Prisma Studio's local server, and includes fixes across Prisma Client and the PostgreSQL, MariaDB, Neon, SQLite, and Prisma Postgres Serverless…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"# Prisma ORM 7.10.0\r\n\r\nPrisma ORM 7.10.0 introduces a compatibility package for running Prisma 7 alongside newer Prisma versions, secures Prisma Studio's local server, and includes fixes across Prisma Client and the PostgreSQL, MariaDB, Neon, SQLite, and Prisma Postgres Serverless adapters.\r\n\r\n## Highlights\r\n\r\n### Run Prisma 7 alongside Prisma 8\r\n\r\nThis release introduces `@prisma/prisma7`, a compatibility package that lets you retain a matching Prisma 7 CLI and configuration while installing Prisma 8 in the same project.\r\n\r\nOnce 7.10.0 is released, a side-by-side installation can use:\r\n\r\n```sh\r\nnpm install --save-dev prisma@8 @prisma/prisma7@7.10.0\r\nnpm install @prisma/client@7.10.0\r\n```\r\n\r\nUse `prisma` for the directly installed Prisma 8 CLI and `prisma7` for Prisma 7:\r\n\r\n```sh\r\nnpx prisma --version\r\nnpx prisma7 --version\r\n\r\nnpx prisma7 generate\r\nnpx prisma7 migrate dev\r\nnpx prisma7 db push\r\n```\r\n\r\nPrisma 7 now prefers version-specific configuration files, allowing its configuration to coexist with Prisma 8's `prisma.config.*` files:\r\n\r\n```ts\r\n// prisma7.config.ts\r\nimport { defineConfig } from '@prisma/prisma7/config'\r\n\r\nexport default defineConfig({\r\n  schema: 'prisma/schema.prisma',\r\n  migrations: {\r\n    path: 'prisma/migrations',\r\n  },\r\n})\r\n```\r\n\r\nWithout an explicit `--config` option, Prisma 7 searches for:\r\n\r\n1. Root-level `prisma7.config.*` files.\r\n2. `.config/prisma7.*` files.\r\n3. Existing `prisma.config.*` files as a backwards-compatible fallback.\r\n\r\nThe supported extensions are `.js`, `.ts`, `.mjs`, `.cjs`, `.mts`, and `.cts`. An explicit config path always takes precedence:\r\n\r\n```sh\r\nnpx prisma7 generate --config ./custom/prisma7.config.ts\r\n```\r\n\r\nNew projects initialized by the Prisma 7 CLI use `prisma7.config.ts`. Existing projects containing only `prisma.config.*` continue to work without migration or additional warnings. If a `prisma7.config.*` file exists but cannot be loaded, Prisma reports the error rather than silently falling back to another configuration.\r\n\r\nThe `prisma7` identity is carried through CLI help, version output, shell completion, initialization, migration, database, and generation guidance. Stable Prisma concepts such as `schema.prisma`, Prisma Migrate, `@prisma/client`, and `PRISMA_*` environment variables remain unchanged.\r\n\r\nTogether, the separate executable and configuration namespace make it possible to operate Prisma 7 and Prisma 8 side by side without command or config-file collisions.\r\n\r\n[#29949](https://github.com/prisma/prisma/pull/29949), [#29969](https://github.com/prisma/prisma/pull/29969), [#29994](https://github.com/prisma/prisma/pull/29994), [#30000](https://github.com/prisma/prisma/pull/30000), [#30002](https://github.com/prisma/prisma/pull/30002), [#30020](https://github.com/prisma/prisma/pull/30020)\r\n\r\n### Prisma Studio security hardening\r\n\r\nPrisma Studio's local HTTP server now:\r\n\r\n- Binds explicitly to `127.0.0.1` instead of all network interfaces.\r\n- Rejects browser requests from origins other than the active `localhost` or `127.0.0.1` Studio URL.\r\n- No longer returns wildcard CORS headers.\r\n- Applies the same protections across Node.js, Bun, and Deno.\r\n\r\nThis prevents network clients or malicious websites from accessing Studio's database endpoints while Studio is running.\r\n\r\n[#29890](https://github.com/prisma/prisma/pull/29890)\r\n\r\n## Prisma Client\r\n\r\n- Fixed `P2002` errors from nested writes so `meta.modelName` identifies the model where the unique constraint violation occurred, including models using `@@map` and `@@schema`. [#29628](https://github.com/prisma/prisma/pull/29628)\r\n- Fixed automatically batched `findUniqueOrThrow()` calls so every missing record rejects with `P2025`; later misses no longer resolve to `undefined`. [#29654](https://github.com/prisma/prisma/pull/29654)\r\n- Parameter-chunked statements are now executed atomically in a transaction and rolled back if a later chunk fails. [#29771](https://github.com/prisma/prisma/pull/29771)\r\n- Improved interactive transaction cleanup during `$disconnect()`, including transactions whose driver-level startup is still in progress. [#28768](https://github.com/prisma/prisma/pull/28768)\r\n- Prevented transaction cleanup failures after a timeout or backend termination from becoming unhandled promise rejections. [#29611](https://github.com/prisma/prisma/pull/29611)\r\n- Fixed fluent relation queries when relation fields are literally named `select` or `include`. [#29683](https://github.com/prisma/prisma/pull/29683)\r\n- Fixed handling of `Date` and `Uint8Array` values created in other JavaScript realms, such as iframes, jsdom, and Node.js `vm` contexts. [#29177](https://github.com/prisma/prisma/pull/29177)\r\n- Invalid `Date` values passed to `$queryRaw` or `$executeRaw` now throw `PrismaClientValidationError` instead of a generic error. [#29718](https://github.com/prisma/prisma/pull/29718)\r\n- Fixed `moduleFormat` inference for the `prisma-client` generator in TypeScript projects using `module: \"node16\"` or `\"nodenext\"`. Generated output now follows the nearest `package.json` `type`, defaulting to CommonJS when absent. [#29712](https://github.com/prisma/prisma/pull/29712)\r\n- Deserialized `Bytes` values now own standalone `ArrayBuffer`s rather than exposing unrelated contents from Node.js's shared `Buffer` pool. This applies to both regular and raw query results. [#29701](https://github.com/prisma/prisma/pull/29701)\r\n- Fixed an incorrect logging context in the remote executor, including Accelerate-backed query execution. [#28892](https://github.com/prisma/prisma/pull/28892)\r\n\r\n## Client extensions and observability\r\n\r\n- Result-extension `compute` callbacks now receive the current model name as a typed second argument:\r\n\r\n  ```ts\r\n  compute(data, modelName) {\r\n    // ...\r\n  }\r\n  ```\r\n\r\n  The model name is also preserved when multiple extensions compose the same computed field. [#29782](https://github.com/prisma/prisma/pull/29782)\r\n\r\n- Improved OpenTelemetry context for remotely executed queries:\r\n  - `$on('query')` callbacks run within the matching `db_query` span.\r\n  - Events from one operation share the same trace.\r\n  - Error events are recorded as span exceptions.\r\n  - Log events continue to be emitted when tracing is disabled or their reported span is unavailable.\r\n\r\n  [#28892](https://github.com/prisma/prisma/pull/28892)\r\n\r\n## Driver adapters\r\n\r\n### MariaDB\r\n\r\n- `@prisma/adapter-mariadb` now accepts an existing `mariadb` pool. External pools remain caller-owned unless `disposeExternalPool: true` is supplied. [#27992](https://github.com/prisma/prisma/pull/27992)\r\n- Fixed pooled connection leaks during commit, rollback, and failed transaction startup. Connections are now returned with `release()` and transaction-specific listeners are removed before reuse. [#29612](https://github.com/prisma/prisma/pull/29612)\r\n- Added support for bracketed IPv6 addresses in both `mysql://` and `mariadb://` connection strings. [#29026](https://github.com/prisma/prisma/pull/29026)\r\n- Prevented malformed connection strings from exposing embedded passwords in retained debug output and diagnostic reports. [#27992](https://github.com/prisma/prisma/pull/27992)\r\n\r\n### PostgreSQL, Neon, and Prisma Postgres Serverless\r\n\r\n- PostgreSQL deadlocks using SQLSTATE `40P01` are now reported as `P2034` transaction write conflicts. [#29717](https://github.com/prisma/prisma/pull/29717)\r\n- PostgreSQL `RESTRICT` violations using SQLSTATE `23001` are now reported as `P2003`, preserving an available field or constraint name. [#29554](https://github.com/prisma/prisma/pull/29554)\r\n- `@prisma/adapter-pg` now preserves database constraint names when reporting unique constraint violations through `P2002`. [#29587](https://github.com/prisma/prisma/pull/29587)\r\n- Prisma Postgres Serverless now prefers the named constraint for `P2002`, falling back to parsed field names when no constraint name is available. [#29801](https://github.com/prisma/prisma/pull/29801)\r\n- Fixed Neon HTTP adapter serialization for typed parameters such as `Bytes` and `DateTime`. [#29747](https://github.com/prisma/prisma/pull/29747)\r\n\r\n### SQLite\r\n\r\n- `@prisma/adapter-better-sqlite3` now converts previously unhandled SQLite result codes into typed database errors instead of exposing raw driver errors.\r\n- The complete `SQLITE_BUSY` family is now mapped to socket timeout errors, with numeric extended result codes preserved where available.\r\n\r\n[#29794](https://github.com/prisma/prisma/pull/29794)\r\n\r\n## CLI and Migrate\r\n\r\n- `prisma generate` can now offer to install Prisma's agent skills. The opt-in prompt:\r\n  - Is shown at most once per machine.\r\n  - Is skipped in CI, containers, Git hooks, npm lifecycle scripts, and watch mode.\r\n  - Is skipped when `--no-hints` is used or Prisma skills are already installed.\r\n  - Times out after 30 seconds.\r\n  - Never causes generation to fail if installation is unsuccessful.\r\n\r\n  [#29690](https://github.com/prisma/prisma/pull/29690)\r\n\r\n- A globally installed CLI now warns during `prisma generate` when its version differs from the project's local `prisma` or `@prisma/client`, and recommends running the local CLI. The check is best-effort and does not fail generation. [#29593](https://github.com/prisma/prisma/pull/29593)\r\n- `prisma version` and `prisma version --json` now include the resolved Prisma CLI package path, making global-versus-local installation issues easier to diagnose. [#29573](https://github.com/prisma/prisma/pull/29573)\r\n- Empty or generator-only schema files now report `Schema must contain a datasource block` from `db pull`, `db push`, and `migrate dev`, rather than reaching the schema engine and potentially producing inconsistent errors. [#29657](https://github.com/prisma/prisma/pull/29657)\r\n- CLI commands now tolerate corrupt, unreadable, or unwritable command-state files. Invalid state is reinitialized, writes are atomic, and persistence failures fall back to in-memory state. [#29609](https://github.com/prisma/prisma/pull/29609)\r\n- Studio now recognizes semicolon-delimited `sqlserver://` connection strings before reporting the existing explicit message that SQL Server is not supported by Studio. [#29623](https://github.com/prisma/prisma/pull/29623)\r\n- The AI-agent safety checkpoint now also covers interactive `prisma db push` confirmations involving data-loss warnings, rather than only invocations using `--accept-data-loss`. [#29793](https://github.com/prisma/prisma/pull/29793)\r\n\r\n## Performance and reliability\r\n\r\n- Optimized query-plan execution by eagerly evaluating plans with one unconditional database operation and synchronously interpreting the remaining pure plan. Cached plans remain immutable. [#29004](https://github.com/prisma/prisma/pull/29004)\r\n- Prevented call-stack overflows when rendering very large parameter lists or combining chunked results containing hundreds of thousands of rows. [#29751](https://github.com/prisma/prisma/pull/29751)\r\n- Reduced ordinary query setup overhead by constructing fluent-relation field maps lazily and in linear time. Non-fluent queries no longer build this map. [#29752](https://github.com/prisma/prisma/pull/29752)\r\n\r\n## Dependencies\r\n\r\n- Updated the transitive `fast-uri` dependency to a patched release addressing production audit advisories affecting versions through `3.1.3`. [#29758](https://github.com/prisma/prisma/pull/29758)\r\n","publishedAt":"2026-08-25T12:54:43.000Z","fetchedAt":"2026-08-26T10:01:53.460Z","url":"https://github.com/prisma/orm/releases/tag/7.10.0","media":[],"coverageCount":0},{"id":"rel_30TU6l8jNBbEhLewYkwCr","version":"7.10.0","type":"feature","title":"7.10.0","summary":"Prisma ORM 7.10.0 Prisma ORM 7.10.0 introduces a compatibility package for running Prisma 7 alongside newer Prisma versions, secures Prisma Studio's local server, and includes fixes across Prisma Client and the PostgreSQL, MariaDB, Neon, SQLite, and Prisma Postgres Serverless…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"# Prisma ORM 7.10.0\r\n\r\nPrisma ORM 7.10.0 introduces a compatibility package for running Prisma 7 alongside newer Prisma versions, secures Prisma Studio's local server, and includes fixes across Prisma Client and the PostgreSQL, MariaDB, Neon, SQLite, and Prisma Postgres Serverless adapters.\r\n\r\n## Highlights\r\n\r\n### Run Prisma 7 alongside Prisma 8\r\n\r\nThis release introduces `@prisma/prisma7`, a compatibility package that lets you retain a matching Prisma 7 CLI and configuration while installing Prisma 8 in the same project.\r\n\r\nOnce 7.10.0 is released, a side-by-side installation can use:\r\n\r\n```sh\r\nnpm install --save-dev prisma@8 @prisma/prisma7@7.10.0\r\nnpm install @prisma/client@7.10.0\r\n```\r\n\r\nUse `prisma` for the directly installed Prisma 8 CLI and `prisma7` for Prisma 7:\r\n\r\n```sh\r\nnpx prisma --version\r\nnpx prisma7 --version\r\n\r\nnpx prisma7 generate\r\nnpx prisma7 migrate dev\r\nnpx prisma7 db push\r\n```\r\n\r\nPrisma 7 now prefers version-specific configuration files, allowing its configuration to coexist with Prisma 8's `prisma.config.*` files:\r\n\r\n```ts\r\n// prisma7.config.ts\r\nimport { defineConfig } from '@prisma/prisma7/config'\r\n\r\nexport default defineConfig({\r\n  schema: 'prisma/schema.prisma',\r\n  migrations: {\r\n    path: 'prisma/migrations',\r\n  },\r\n})\r\n```\r\n\r\nWithout an explicit `--config` option, Prisma 7 searches for:\r\n\r\n1. Root-level `prisma7.config.*` files.\r\n2. `.config/prisma7.*` files.\r\n3. Existing `prisma.config.*` files as a backwards-compatible fallback.\r\n\r\nThe supported extensions are `.js`, `.ts`, `.mjs`, `.cjs`, `.mts`, and `.cts`. An explicit config path always takes precedence:\r\n\r\n```sh\r\nnpx prisma7 generate --config ./custom/prisma7.config.ts\r\n```\r\n\r\nNew projects initialized by the Prisma 7 CLI use `prisma7.config.ts`. Existing projects containing only `prisma.config.*` continue to work without migration or additional warnings. If a `prisma7.config.*` file exists but cannot be loaded, Prisma reports the error rather than silently falling back to another configuration.\r\n\r\nThe `prisma7` identity is carried through CLI help, version output, shell completion, initialization, migration, database, and generation guidance. Stable Prisma concepts such as `schema.prisma`, Prisma Migrate, `@prisma/client`, and `PRISMA_*` environment variables remain unchanged.\r\n\r\nTogether, the separate executable and configuration namespace make it possible to operate Prisma 7 and Prisma 8 side by side without command or config-file collisions.\r\n\r\n[#29949](https://github.com/prisma/prisma/pull/29949), [#29969](https://github.com/prisma/prisma/pull/29969), [#29994](https://github.com/prisma/prisma/pull/29994), [#30000](https://github.com/prisma/prisma/pull/30000), [#30002](https://github.com/prisma/prisma/pull/30002), [#30020](https://github.com/prisma/prisma/pull/30020)\r\n\r\n### Prisma Studio security hardening\r\n\r\nPrisma Studio's local HTTP server now:\r\n\r\n- Binds explicitly to `127.0.0.1` instead of all network interfaces.\r\n- Rejects browser requests from origins other than the active `localhost` or `127.0.0.1` Studio URL.\r\n- No longer returns wildcard CORS headers.\r\n- Applies the same protections across Node.js, Bun, and Deno.\r\n\r\nThis prevents network clients or malicious websites from accessing Studio's database endpoints while Studio is running.\r\n\r\n[#29890](https://github.com/prisma/prisma/pull/29890)\r\n\r\n## Prisma Client\r\n\r\n- Fixed `P2002` errors from nested writes so `meta.modelName` identifies the model where the unique constraint violation occurred, including models using `@@map` and `@@schema`. [#29628](https://github.com/prisma/prisma/pull/29628)\r\n- Fixed automatically batched `findUniqueOrThrow()` calls so every missing record rejects with `P2025`; later misses no longer resolve to `undefined`. [#29654](https://github.com/prisma/prisma/pull/29654)\r\n- Parameter-chunked statements are now executed atomically in a transaction and rolled back if a later chunk fails. [#29771](https://github.com/prisma/prisma/pull/29771)\r\n- Improved interactive transaction cleanup during `$disconnect()`, including transactions whose driver-level startup is still in progress. [#28768](https://github.com/prisma/prisma/pull/28768)\r\n- Prevented transaction cleanup failures after a timeout or backend termination from becoming unhandled promise rejections. [#29611](https://github.com/prisma/prisma/pull/29611)\r\n- Fixed fluent relation queries when relation fields are literally named `select` or `include`. [#29683](https://github.com/prisma/prisma/pull/29683)\r\n- Fixed handling of `Date` and `Uint8Array` values created in other JavaScript realms, such as iframes, jsdom, and Node.js `vm` contexts. [#29177](https://github.com/prisma/prisma/pull/29177)\r\n- Invalid `Date` values passed to `$queryRaw` or `$executeRaw` now throw `PrismaClientValidationError` instead of a generic error. [#29718](https://github.com/prisma/prisma/pull/29718)\r\n- Fixed `moduleFormat` inference for the `prisma-client` generator in TypeScript projects using `module: \"node16\"` or `\"nodenext\"`. Generated output now follows the nearest `package.json` `type`, defaulting to CommonJS when absent. [#29712](https://github.com/prisma/prisma/pull/29712)\r\n- Deserialized `Bytes` values now own standalone `ArrayBuffer`s rather than exposing unrelated contents from Node.js's shared `Buffer` pool. This applies to both regular and raw query results. [#29701](https://github.com/prisma/prisma/pull/29701)\r\n- Fixed an incorrect logging context in the remote executor, including Accelerate-backed query execution. [#28892](https://github.com/prisma/prisma/pull/28892)\r\n\r\n## Client extensions and observability\r\n\r\n- Result-extension `compute` callbacks now receive the current model name as a typed second argument:\r\n\r\n  ```ts\r\n  compute(data, modelName) {\r\n    // ...\r\n  }\r\n  ```\r\n\r\n  The model name is also preserved when multiple extensions compose the same computed field. [#29782](https://github.com/prisma/prisma/pull/29782)\r\n\r\n- Improved OpenTelemetry context for remotely executed queries:\r\n  - `$on('query')` callbacks run within the matching `db_query` span.\r\n  - Events from one operation share the same trace.\r\n  - Error events are recorded as span exceptions.\r\n  - Log events continue to be emitted when tracing is disabled or their reported span is unavailable.\r\n\r\n  [#28892](https://github.com/prisma/prisma/pull/28892)\r\n\r\n## Driver adapters\r\n\r\n### MariaDB\r\n\r\n- `@prisma/adapter-mariadb` now accepts an existing `mariadb` pool. External pools remain caller-owned unless `disposeExternalPool: true` is supplied. [#27992](https://github.com/prisma/prisma/pull/27992)\r\n- Fixed pooled connection leaks during commit, rollback, and failed transaction startup. Connections are now returned with `release()` and transaction-specific listeners are removed before reuse. [#29612](https://github.com/prisma/prisma/pull/29612)\r\n- Added support for bracketed IPv6 addresses in both `mysql://` and `mariadb://` connection strings. [#29026](https://github.com/prisma/prisma/pull/29026)\r\n- Prevented malformed connection strings from exposing embedded passwords in retained debug output and diagnostic reports. [#27992](https://github.com/prisma/prisma/pull/27992)\r\n\r\n### PostgreSQL, Neon, and Prisma Postgres Serverless\r\n\r\n- PostgreSQL deadlocks using SQLSTATE `40P01` are now reported as `P2034` transaction write conflicts. [#29717](https://github.com/prisma/prisma/pull/29717)\r\n- PostgreSQL `RESTRICT` violations using SQLSTATE `23001` are now reported as `P2003`, preserving an available field or constraint name. [#29554](https://github.com/prisma/prisma/pull/29554)\r\n- `@prisma/adapter-pg` now preserves database constraint names when reporting unique constraint violations through `P2002`. [#29587](https://github.com/prisma/prisma/pull/29587)\r\n- Prisma Postgres Serverless now prefers the named constraint for `P2002`, falling back to parsed field names when no constraint name is available. [#29801](https://github.com/prisma/prisma/pull/29801)\r\n- Fixed Neon HTTP adapter serialization for typed parameters such as `Bytes` and `DateTime`. [#29747](https://github.com/prisma/prisma/pull/29747)\r\n\r\n### SQLite\r\n\r\n- `@prisma/adapter-better-sqlite3` now converts previously unhandled SQLite result codes into typed database errors instead of exposing raw driver errors.\r\n- The complete `SQLITE_BUSY` family is now mapped to socket timeout errors, with numeric extended result codes preserved where available.\r\n\r\n[#29794](https://github.com/prisma/prisma/pull/29794)\r\n\r\n## CLI and Migrate\r\n\r\n- `prisma generate` can now offer to install Prisma's agent skills. The opt-in prompt:\r\n  - Is shown at most once per machine.\r\n  - Is skipped in CI, containers, Git hooks, npm lifecycle scripts, and watch mode.\r\n  - Is skipped when `--no-hints` is used or Prisma skills are already installed.\r\n  - Times out after 30 seconds.\r\n  - Never causes generation to fail if installation is unsuccessful.\r\n\r\n  [#29690](https://github.com/prisma/prisma/pull/29690)\r\n\r\n- A globally installed CLI now warns during `prisma generate` when its version differs from the project's local `prisma` or `@prisma/client`, and recommends running the local CLI. The check is best-effort and does not fail generation. [#29593](https://github.com/prisma/prisma/pull/29593)\r\n- `prisma version` and `prisma version --json` now include the resolved Prisma CLI package path, making global-versus-local installation issues easier to diagnose. [#29573](https://github.com/prisma/prisma/pull/29573)\r\n- Empty or generator-only schema files now report `Schema must contain a datasource block` from `db pull`, `db push`, and `migrate dev`, rather than reaching the schema engine and potentially producing inconsistent errors. [#29657](https://github.com/prisma/prisma/pull/29657)\r\n- CLI commands now tolerate corrupt, unreadable, or unwritable command-state files. Invalid state is reinitialized, writes are atomic, and persistence failures fall back to in-memory state. [#29609](https://github.com/prisma/prisma/pull/29609)\r\n- Studio now recognizes semicolon-delimited `sqlserver://` connection strings before reporting the existing explicit message that SQL Server is not supported by Studio. [#29623](https://github.com/prisma/prisma/pull/29623)\r\n- The AI-agent safety checkpoint now also covers interactive `prisma db push` confirmations involving data-loss warnings, rather than only invocations using `--accept-data-loss`. [#29793](https://github.com/prisma/prisma/pull/29793)\r\n\r\n## Performance and reliability\r\n\r\n- Optimized query-plan execution by eagerly evaluating plans with one unconditional database operation and synchronously interpreting the remaining pure plan. Cached plans remain immutable. [#29004](https://github.com/prisma/prisma/pull/29004)\r\n- Prevented call-stack overflows when rendering very large parameter lists or combining chunked results containing hundreds of thousands of rows. [#29751](https://github.com/prisma/prisma/pull/29751)\r\n- Reduced ordinary query setup overhead by constructing fluent-relation field maps lazily and in linear time. Non-fluent queries no longer build this map. [#29752](https://github.com/prisma/prisma/pull/29752)\r\n\r\n## Dependencies\r\n\r\n- Updated the transitive `fast-uri` dependency to a patched release addressing production audit advisories affecting versions through `3.1.3`. [#29758](https://github.com/prisma/prisma/pull/29758)\r\n","publishedAt":"2026-08-25T12:54:43.000Z","fetchedAt":"2026-08-25T13:48:12.198Z","url":"https://github.com/prisma/prisma/releases/tag/7.10.0","media":[],"coverageCount":0},{"id":"rel_m7qGcZzsrNwicpEADmGIW","version":"v0.17.0","type":"feature","title":"v0.17.0","summary":"This is the namespace release: Prisma Next now publishes as 17 packages under the @prisma scope, and an application depends on exactly one database facade. It also completes the structured error-code scheme across every plane, makes relation-loading lossless for big numbers and…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"# v0.17.0\n\nThis is the namespace release: Prisma Next now publishes as 17 packages under the `@prisma` scope, and an application depends on exactly one database facade. It also completes the structured error-code scheme across every plane, makes relation-loading lossless for big numbers and temporal values, and gives every SQL index and RLS policy an exact, migratable name.\n\n## Breaking changes\n\n- **One `@prisma` package per application** — the `@prisma-next/*` scope is retired; nothing publishes under it again. An application depends on exactly one database facade — `@prisma/orm-postgres`, `@prisma/orm-sqlite`, or `@prisma/orm-mongo` — plus any extension packs it uses (now named `@prisma/orm-extension-*`); everything else arrives as the facade's exact-pinned dependencies. Regenerating your contract rewrites generated imports to facade entrypoints with no `contractHash` change. See the [0.16-to-0.17 upgrade recipe](https://github.com/prisma/prisma/blob/v0.17.0/skills/upgrade/prisma-next-upgrade/upgrades/0.16-to-0.17/) and the [extension-author recipe](https://github.com/prisma/prisma/blob/v0.17.0/skills/extension-author/prisma-8-extension-upgrade/upgrades/0.16-to-0.17/). ([#29864](https://github.com/prisma/prisma/pull/29864), [#29880](https://github.com/prisma/prisma/pull/29880), [#29883](https://github.com/prisma/prisma/pull/29883), [#29884](https://github.com/prisma/prisma/pull/29884))\n\n  Before:\n\n  ```jsonc\n  \"dependencies\": {\n    \"@prisma-next/postgres\": \"0.16.0\",\n    \"@prisma-next/framework-components\": \"0.16.0\",\n    \"@prisma-next/sql-runtime\": \"0.16.0\"\n  }\n  ```\n\n  After:\n\n  ```jsonc\n  \"dependencies\": {\n    \"@prisma/orm-postgres\": \"0.17.0\"\n  }\n  ```\n\n- **Every published error is a structured envelope with a dotted code** — the four legacy error systems (`PN-CLI-4001`-style codes, `RUNTIME.DECODE_FAILED`-style codes, and codeless error classes) consolidate into one scheme: a structural envelope carrying a `NAMESPACE.SUBCODE` code, recognized by the `isStructuredError` type predicate instead of `instanceof`. The ORM, contract-authoring, adapter/target, extension, and framework planes are all swept; legacy error classes (`PslFormatError`, the Supabase and SQL-escape classes, framework classes) are deleted. Prisma 7's `P1001`-style codes are not carried over. ([#1016](https://github.com/prisma/prisma-next/pull/1016), [#1021](https://github.com/prisma/prisma-next/pull/1021), [#1025](https://github.com/prisma/prisma-next/pull/1025), [#1049](https://github.com/prisma/prisma-next/pull/1049), [#1053](https://github.com/prisma/prisma-next/pull/1053), [#1063](https://github.com/prisma/prisma-next/pull/1063))\n\n  Before:\n\n  ```ts\n  if (error instanceof PslFormatError) {\n    report(error.diagnostics);\n  }\n  ```\n\n  After:\n\n  ```ts\n  if (isStructuredError(error) && error.code === 'PSL.PARSE_FAILED') {\n    report(error.meta.diagnostics);\n  }\n  ```\n\n- **Content hashes are bare hex** — the `sha256:` prefix is gone from every surface (emitted contracts, migration manifests, refs, CLI output, and the database marker), and loaders reject the prefixed form. Contract hash values are unchanged; `migrationHash` values change. A codemod in the [0.16-to-0.17 recipe](https://github.com/prisma/prisma/blob/v0.17.0/skills/upgrade/prisma-next-upgrade/upgrades/0.16-to-0.17/) converts checked-in migration trees. ([#1033](https://github.com/prisma/prisma-next/pull/1033))\n\n- **Migration contract snapshots move into a content-addressed store** — per-migration sibling snapshot files and ref-paired copies are replaced by a single `migrations/snapshots/<hex>/` store per migrations root; every distinct contract is stored once, and `migration.ts` imports its bookend contracts from the store. This is a clean break with no fallback reader; a one-shot migrator (`scripts/migrate-migrations-layout.mjs`) converts existing trees and re-verifies every `migrationHash` unchanged. ([#1018](https://github.com/prisma/prisma-next/pull/1018), [#1024](https://github.com/prisma/prisma-next/pull/1024))\n\n- **PostgreSQL native types are authored in type position; the `@db.*` attribute channel is removed** — write the native type directly (`VarChar(255)`, `Uuid`, `Timestamptz`) instead of a base type plus `@db.*` attribute; remaining `@db.X(args)` usage fails with the exact replacement spelled out. `Json` re-binds to native `json` storage, with a new `Jsonb` scalar for jsonb (what every pre-0.16 `Json` field meant — switch those fields to keep a byte-identical contract), and `Date` re-binds to the correct `pg/date@1` codec. ([#1022](https://github.com/prisma/prisma-next/pull/1022), [#1036](https://github.com/prisma/prisma-next/pull/1036), [#1054](https://github.com/prisma/prisma-next/pull/1054))\n\n  Before:\n\n  ```prisma\n  model User {\n    id    String @id @db.Uuid\n    name  String @db.VarChar(255)\n  }\n  ```\n\n  After:\n\n  ```prisma\n  model User {\n    id    Uuid         @id\n    name  VarChar(255)\n  }\n  ```\n\n- **Relation-loading and aggregates are lossless** — values read through `.include()` no longer pass through lossy JSON: every codec gains an explicit lossless JSON form produced inside the database. 64-bit integers arrive as `bigint` instead of silently rounding, decimals as exact strings, and temporal columns decode correctly. Aggregate result types change accordingly: `count()` is a `bigint`, decimal sums are strings. Regenerate your contract after upgrading. ([#29844](https://github.com/prisma/prisma/pull/29844), [#1023](https://github.com/prisma/prisma-next/pull/1023), [#1051](https://github.com/prisma/prisma-next/pull/1051))\n\n- **SQL indexes and RLS policies are name-identified** — every index and RLS policy carries an exact name in the contract, names travel on the wire, live objects can be adopted by exact name (`@@map`), and a rename converges by renaming instead of drop-and-recreate. ([#1047](https://github.com/prisma/prisma-next/pull/1047), [#29807](https://github.com/prisma/prisma/pull/29807), [#29865](https://github.com/prisma/prisma/pull/29865))\n\n- **`extensionPacks` config key renamed to `extensions`** — in `prisma-next.config.ts`, the TS builder, client options, and the emitted contract's top-level key. The old key fails loudly. Because the key sits in the hashed contract bytes, all contract hashes change: re-emit and re-anchor migrations per the recipe. Two smaller key renames ride along: `contract.source.sourceFormat` → `format`, and the facade `defineConfig` option `outputPath` → `output`. ([#1032](https://github.com/prisma/prisma-next/pull/1032))\n\n- **Count-only mutation terminals renamed** — `createCount(...)` / `updateCount(...)` / `deleteCount()` become `createAndCount(...)` / `updateAndCount(...)` / `deleteAndCount()`; behavior and `Promise<number>` results are unchanged, with no compatibility aliases. ([#1044](https://github.com/prisma/prisma-next/pull/1044))\n\n## Features\n\n- Expression, partial, and unique indexes are authorable in both PSL and the TypeScript builder. ([#1048](https://github.com/prisma/prisma-next/pull/1048))\n- `contract infer` reaches full fidelity — indexes, policy blocks, and `@@rls` are captured — and signs the database, so introspect-then-verify works end to end on an adopted database. It also infers 1:1 relations from unique indexes. ([#29808](https://github.com/prisma/prisma/pull/29808), [#1038](https://github.com/prisma/prisma-next/pull/1038))\n- Every error code is documented on an in-repo reference page (221 codes), kept complete by a CI check, and error envelopes carry a `docsUrl` pointing at their per-code anchor. ([#1027](https://github.com/prisma/prisma-next/pull/1027), [#29806](https://github.com/prisma/prisma/pull/29806))\n\n## Fixes\n\n- MongoDB write results decode through their type codecs instead of returning raw wire values. ([#29879](https://github.com/prisma/prisma/pull/29879))\n- The Postgres runtime driver serializes queries per pinned client, fixing interleaved-query failures on a shared connection. ([#29839](https://github.com/prisma/prisma/pull/29839))\n- Mixed-case native-enum casts are quoted, so PascalCase enum type names survive Postgres case-folding. ([#1034](https://github.com/prisma/prisma-next/pull/1034))\n- Driver cursor streaming runs inside an explicit transaction, fixing dropped-portal failures under load. ([#1017](https://github.com/prisma/prisma-next/pull/1017))\n- Published type declarations name only dependencies a consumer will actually have installed. ([#29862](https://github.com/prisma/prisma/pull/29862))\n","publishedAt":"2026-08-04T13:31:06.000Z","fetchedAt":"2026-08-26T10:01:54.038Z","url":"https://github.com/prisma/orm/releases/tag/v0.17.0","media":[],"coverageCount":0},{"id":"rel_uPULEIk0rf0erfTdzdG5i","version":"v0.17.0","type":"feature","title":"v0.17.0","summary":"This is the namespace release: Prisma Next now publishes as 17 packages under the @prisma scope, and an application depends on exactly one database facade. It also completes the structured error-code scheme across every plane, makes relation-loading lossless for big numbers and…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"# v0.17.0\n\nThis is the namespace release: Prisma Next now publishes as 17 packages under the `@prisma` scope, and an application depends on exactly one database facade. It also completes the structured error-code scheme across every plane, makes relation-loading lossless for big numbers and temporal values, and gives every SQL index and RLS policy an exact, migratable name.\n\n## Breaking changes\n\n- **One `@prisma` package per application** — the `@prisma-next/*` scope is retired; nothing publishes under it again. An application depends on exactly one database facade — `@prisma/orm-postgres`, `@prisma/orm-sqlite`, or `@prisma/orm-mongo` — plus any extension packs it uses (now named `@prisma/orm-extension-*`); everything else arrives as the facade's exact-pinned dependencies. Regenerating your contract rewrites generated imports to facade entrypoints with no `contractHash` change. See the [0.16-to-0.17 upgrade recipe](https://github.com/prisma/prisma/blob/v0.17.0/skills/upgrade/prisma-next-upgrade/upgrades/0.16-to-0.17/) and the [extension-author recipe](https://github.com/prisma/prisma/blob/v0.17.0/skills/extension-author/prisma-8-extension-upgrade/upgrades/0.16-to-0.17/). ([#29864](https://github.com/prisma/prisma/pull/29864), [#29880](https://github.com/prisma/prisma/pull/29880), [#29883](https://github.com/prisma/prisma/pull/29883), [#29884](https://github.com/prisma/prisma/pull/29884))\n\n  Before:\n\n  ```jsonc\n  \"dependencies\": {\n    \"@prisma-next/postgres\": \"0.16.0\",\n    \"@prisma-next/framework-components\": \"0.16.0\",\n    \"@prisma-next/sql-runtime\": \"0.16.0\"\n  }\n  ```\n\n  After:\n\n  ```jsonc\n  \"dependencies\": {\n    \"@prisma/orm-postgres\": \"0.17.0\"\n  }\n  ```\n\n- **Every published error is a structured envelope with a dotted code** — the four legacy error systems (`PN-CLI-4001`-style codes, `RUNTIME.DECODE_FAILED`-style codes, and codeless error classes) consolidate into one scheme: a structural envelope carrying a `NAMESPACE.SUBCODE` code, recognized by the `isStructuredError` type predicate instead of `instanceof`. The ORM, contract-authoring, adapter/target, extension, and framework planes are all swept; legacy error classes (`PslFormatError`, the Supabase and SQL-escape classes, framework classes) are deleted. Prisma 7's `P1001`-style codes are not carried over. ([#1016](https://github.com/prisma/prisma-next/pull/1016), [#1021](https://github.com/prisma/prisma-next/pull/1021), [#1025](https://github.com/prisma/prisma-next/pull/1025), [#1049](https://github.com/prisma/prisma-next/pull/1049), [#1053](https://github.com/prisma/prisma-next/pull/1053), [#1063](https://github.com/prisma/prisma-next/pull/1063))\n\n  Before:\n\n  ```ts\n  if (error instanceof PslFormatError) {\n    report(error.diagnostics);\n  }\n  ```\n\n  After:\n\n  ```ts\n  if (isStructuredError(error) && error.code === 'PSL.PARSE_FAILED') {\n    report(error.meta.diagnostics);\n  }\n  ```\n\n- **Content hashes are bare hex** — the `sha256:` prefix is gone from every surface (emitted contracts, migration manifests, refs, CLI output, and the database marker), and loaders reject the prefixed form. Contract hash values are unchanged; `migrationHash` values change. A codemod in the [0.16-to-0.17 recipe](https://github.com/prisma/prisma/blob/v0.17.0/skills/upgrade/prisma-next-upgrade/upgrades/0.16-to-0.17/) converts checked-in migration trees. ([#1033](https://github.com/prisma/prisma-next/pull/1033))\n\n- **Migration contract snapshots move into a content-addressed store** — per-migration sibling snapshot files and ref-paired copies are replaced by a single `migrations/snapshots/<hex>/` store per migrations root; every distinct contract is stored once, and `migration.ts` imports its bookend contracts from the store. This is a clean break with no fallback reader; a one-shot migrator (`scripts/migrate-migrations-layout.mjs`) converts existing trees and re-verifies every `migrationHash` unchanged. ([#1018](https://github.com/prisma/prisma-next/pull/1018), [#1024](https://github.com/prisma/prisma-next/pull/1024))\n\n- **PostgreSQL native types are authored in type position; the `@db.*` attribute channel is removed** — write the native type directly (`VarChar(255)`, `Uuid`, `Timestamptz`) instead of a base type plus `@db.*` attribute; remaining `@db.X(args)` usage fails with the exact replacement spelled out. `Json` re-binds to native `json` storage, with a new `Jsonb` scalar for jsonb (what every pre-0.16 `Json` field meant — switch those fields to keep a byte-identical contract), and `Date` re-binds to the correct `pg/date@1` codec. ([#1022](https://github.com/prisma/prisma-next/pull/1022), [#1036](https://github.com/prisma/prisma-next/pull/1036), [#1054](https://github.com/prisma/prisma-next/pull/1054))\n\n  Before:\n\n  ```prisma\n  model User {\n    id    String @id @db.Uuid\n    name  String @db.VarChar(255)\n  }\n  ```\n\n  After:\n\n  ```prisma\n  model User {\n    id    Uuid         @id\n    name  VarChar(255)\n  }\n  ```\n\n- **Relation-loading and aggregates are lossless** — values read through `.include()` no longer pass through lossy JSON: every codec gains an explicit lossless JSON form produced inside the database. 64-bit integers arrive as `bigint` instead of silently rounding, decimals as exact strings, and temporal columns decode correctly. Aggregate result types change accordingly: `count()` is a `bigint`, decimal sums are strings. Regenerate your contract after upgrading. ([#29844](https://github.com/prisma/prisma/pull/29844), [#1023](https://github.com/prisma/prisma-next/pull/1023), [#1051](https://github.com/prisma/prisma-next/pull/1051))\n\n- **SQL indexes and RLS policies are name-identified** — every index and RLS policy carries an exact name in the contract, names travel on the wire, live objects can be adopted by exact name (`@@map`), and a rename converges by renaming instead of drop-and-recreate. ([#1047](https://github.com/prisma/prisma-next/pull/1047), [#29807](https://github.com/prisma/prisma/pull/29807), [#29865](https://github.com/prisma/prisma/pull/29865))\n\n- **`extensionPacks` config key renamed to `extensions`** — in `prisma-next.config.ts`, the TS builder, client options, and the emitted contract's top-level key. The old key fails loudly. Because the key sits in the hashed contract bytes, all contract hashes change: re-emit and re-anchor migrations per the recipe. Two smaller key renames ride along: `contract.source.sourceFormat` → `format`, and the facade `defineConfig` option `outputPath` → `output`. ([#1032](https://github.com/prisma/prisma-next/pull/1032))\n\n- **Count-only mutation terminals renamed** — `createCount(...)` / `updateCount(...)` / `deleteCount()` become `createAndCount(...)` / `updateAndCount(...)` / `deleteAndCount()`; behavior and `Promise<number>` results are unchanged, with no compatibility aliases. ([#1044](https://github.com/prisma/prisma-next/pull/1044))\n\n## Features\n\n- Expression, partial, and unique indexes are authorable in both PSL and the TypeScript builder. ([#1048](https://github.com/prisma/prisma-next/pull/1048))\n- `contract infer` reaches full fidelity — indexes, policy blocks, and `@@rls` are captured — and signs the database, so introspect-then-verify works end to end on an adopted database. It also infers 1:1 relations from unique indexes. ([#29808](https://github.com/prisma/prisma/pull/29808), [#1038](https://github.com/prisma/prisma-next/pull/1038))\n- Every error code is documented on an in-repo reference page (221 codes), kept complete by a CI check, and error envelopes carry a `docsUrl` pointing at their per-code anchor. ([#1027](https://github.com/prisma/prisma-next/pull/1027), [#29806](https://github.com/prisma/prisma/pull/29806))\n\n## Fixes\n\n- MongoDB write results decode through their type codecs instead of returning raw wire values. ([#29879](https://github.com/prisma/prisma/pull/29879))\n- The Postgres runtime driver serializes queries per pinned client, fixing interleaved-query failures on a shared connection. ([#29839](https://github.com/prisma/prisma/pull/29839))\n- Mixed-case native-enum casts are quoted, so PascalCase enum type names survive Postgres case-folding. ([#1034](https://github.com/prisma/prisma-next/pull/1034))\n- Driver cursor streaming runs inside an explicit transaction, fixing dropped-portal failures under load. ([#1017](https://github.com/prisma/prisma-next/pull/1017))\n- Published type declarations name only dependencies a consumer will actually have installed. ([#29862](https://github.com/prisma/prisma/pull/29862))\n","publishedAt":"2026-08-04T13:31:06.000Z","fetchedAt":"2026-08-04T16:28:10.313Z","url":"https://github.com/prisma/prisma/releases/tag/v0.17.0","media":[],"coverageCount":0},{"id":"rel_6K8mcuq1Dxz6er1u5Y3WD","version":"7.9.1","type":"feature","title":"7.9.1","summary":"Today, we're issuing a patch release to resolve a security advisory in a transitive dependency of Prisma CLI (via @prisma/dev). This fixes https://github.com/prisma/prisma/issues/29780. It does not actually affect @prisma/dev or Prisma CLI so no urgent action is required, but…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"Today, we're issuing a patch release to resolve a security advisory in a transitive dependency of Prisma CLI (via `@prisma/dev`).\r\n\r\nThis fixes https://github.com/prisma/prisma/issues/29780.\r\n\r\nIt does not actually affect `@prisma/dev` or Prisma CLI so no urgent action is required, but it is recommended to upgrade nevertheless to avoid false positives from security scanners.","publishedAt":"2026-07-27T14:17:54.000Z","fetchedAt":"2026-08-26T10:01:54.633Z","url":"https://github.com/prisma/orm/releases/tag/7.9.1","media":[],"coverageCount":0},{"id":"rel_94_bznKoxFzAls554gxCC","version":"7.9.1","type":"feature","title":"7.9.1","summary":"Today, we're issuing a patch release to resolve a security advisory in a transitive dependency of Prisma CLI (via @prisma/dev). This fixes https://github.com/prisma/prisma/issues/29780. It does not actually affect @prisma/dev or Prisma CLI so no urgent action is required, but…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"Today, we're issuing a patch release to resolve a security advisory in a transitive dependency of Prisma CLI (via `@prisma/dev`).\r\n\r\nThis fixes https://github.com/prisma/prisma/issues/29780.\r\n\r\nIt does not actually affect `@prisma/dev` or Prisma CLI so no urgent action is required, but it is recommended to upgrade nevertheless to avoid false positives from security scanners.","publishedAt":"2026-07-27T14:17:54.000Z","fetchedAt":"2026-07-27T14:24:19.484Z","url":"https://github.com/prisma/prisma/releases/tag/7.9.1","media":[],"coverageCount":0},{"id":"rel_nTj1rejPvF61Uzl9WcHag","version":"7.9.0","type":"feature","title":"7.9.0","summary":"Today, we are excited to share the 7.9.0 stable release 🎉 🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X! Highlights ORM Tab completions for the Prisma CLI Typing out CLI commands from memory is now optional. Prisma ships shell…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"Today, we are excited to share the `7.9.0` stable release 🎉\r\n\r\n**🌟 Star this repo for notifications about new releases, bug fixes & features — or [follow us on X](https://pris.ly/x)!**\r\n\r\n# Highlights\r\n\r\n## ORM\r\n\r\n### Tab completions for the Prisma CLI\r\n\r\nTyping out CLI commands from memory is now optional. Prisma ships **shell tab completions** for `bash`, `zsh`, `fish`, and PowerShell, covering commands, subcommands, options, flags, and even option values.\r\n\r\n**Setting it up.** Most projects run Prisma through a package manager, so completions are enabled through `@bomb.sh/tab`'s package-manager integration — install it once, then source the completion for your package manager and shell:\r\n\r\n```bash\r\n# 1. Install @bomb.sh/tab globally\r\nnpm install -g @bomb.sh/tab\r\n\r\n# 2. Wire up your package manager + shell (pnpm shown; swap in npm / yarn / bun):\r\necho 'source <(tab pnpm zsh)'  >> ~/.zshrc            # zsh\r\necho 'source <(tab pnpm bash)' >> ~/.bashrc           # bash\r\ntab pnpm fish > ~/.config/fish/completions/pnpm.fish  # fish\r\ntab pnpm powershell > ~/.tab-pnpm.ps1                 # PowerShell (then dot-source it from $PROFILE)\r\n```\r\n\r\n`@bomb.sh/tab` delegates to any locally-installed CLI that ships completions, so `pnpm prisma <TAB>`, `pnpm exec prisma <TAB>`, `yarn prisma <TAB>`, and `bun x prisma <TAB>` all complete Prisma's commands, options, and values — no per-project setup. (`npx` and `bunx` don't support completion themselves; use `npm exec` and `bun x`.)\r\n\r\nIf instead you have Prisma installed globally on your `PATH`, source its own completion directly: `source <(prisma complete zsh)` (or the `bash` / `fish` / `powershell` variant).\r\n\r\nThis is built on [`@bomb.sh/tab`](https://github.com/bombshell-dev/tab/), the same completion library that powers other CLIs in the ecosystem — including Cloudflare, Nuxt, and Vitest — so the package-manager completions you enable for Prisma work for those tools too. A wonderful community contribution from [@AmirSa12](https://github.com/AmirSa12) ([#28351](https://github.com/prisma/prisma/pull/28351)) — thank you!\r\n\r\nhttps://github.com/user-attachments/assets/1f916a60-ee4d-40be-bb7d-74035d48ca83\r\n\r\n### Prisma ORM, ready for AI agents\r\n\r\nCoding agents are now a first-class audience for Prisma, and 7.9.0 brings the first wave of work to make Prisma projects safe and productive for them to work in.\r\n\r\n**Agent skills installed with `prisma init`** ([#29689](https://github.com/prisma/prisma/pull/29689))\r\n\r\n`prisma init` now installs the [prisma/skills](https://github.com/prisma/skills) catalog into freshly scaffolded projects. Agents such as Claude Code, Cursor, Codex, and Windsurf start out with current, version-relevant Prisma knowledge instead of relying on whatever happened to be in their training data. The install is best-effort and never blocks scaffolding; opt out at any time with `--no-skills`.\r\n\r\n```terminal\r\nnpx prisma@latest init\r\n```\r\n\r\n![prisma init scaffolds a project and installs the Prisma agent skills catalog](https://github.com/user-attachments/assets/8244a6dc-cdad-4028-a652-bb5ac6e4b271)\r\n\r\n**A safer default around destructive commands** ([#29684](https://github.com/prisma/prisma/pull/29684), [#29691](https://github.com/prisma/prisma/pull/29691), [#29713](https://github.com/prisma/prisma/pull/29713))\r\n\r\nPrisma's AI safety checkpoint refuses to run destructive commands when it detects that an AI agent is at the keyboard, unless the user has given explicit consent. In this release we:\r\n\r\n- **Broadened agent detection** to cover today's landscape — Codex CLI (now on Linux as well as macOS), Qwen Code, GitHub Copilot CLI, OpenCode, Cline, Goose, Amp, Crush, Augment Code, Antigravity, Replit Agent, and Devin — plus generic `AI_AGENT` / `AGENT` conventions so future agents are caught without a code change.\r\n- **Extended the guard to `db push --accept-data-loss`**, which previously bypassed the checkpoint even though it can drop data.\r\n- **Removed the `migrate-reset` tool from the `prisma mcp` server** entirely — resetting a database drops it, and that is not an operation an agent should be handed as a first-class tool. An agent that needs a reset must run the CLI, where the checkpoint applies.\r\n\r\n### Bug Fixes\r\n\r\nMany of the fixes below are **community contributions** — thank you to everyone who reported and fixed these!\r\n\r\n**Prisma Client**\r\n\r\n- Fixed a severe TypeScript performance regression introduced in Prisma 7: restoring the `OmitOpts` generic default lets `tsc` reuse cached type instantiations again, bringing type-checking on large schemas back from minutes to seconds ([#29592](https://github.com/prisma/prisma/pull/29592), from [@nfl1ryxditimo12](https://github.com/nfl1ryxditimo12)).\r\n- The `XOR` type helper now rejects primitive values such as `data: 5`, which were previously accepted at compile time even though the runtime rejected them ([#29735](https://github.com/prisma/prisma/pull/29735), from [@kyungseopk1m](https://github.com/kyungseopk1m)).\r\n- `$queryRaw` and `$executeRaw` now fail fast with a clear validation error when passed an invalid `Date`, instead of silently serializing it as `null` and corrupting the value sent to the database ([#29697](https://github.com/prisma/prisma/pull/29697), from [@jibin7jose](https://github.com/jibin7jose)).\r\n- The generated client is no longer corrupted by a `///` documentation comment that contains a `*/` sequence; the comment terminator is now escaped when doc comments are emitted, in both the TypeScript and JavaScript generators ([#29736](https://github.com/prisma/prisma/pull/29736), from [@kyungseopk1m](https://github.com/kyungseopk1m)).\r\n- Improved the runtime and TypeScript error messages shown when a driver adapter is missing from the `PrismaClient` constructor; both now include a copy-pasteable example and a link to the [driver adapters docs](https://pris.ly/d/driver-adapters) ([#29624](https://github.com/prisma/prisma/pull/29624)).\r\n- Unmapped database errors from driver adapters now surface as a user-facing `P2039` (`PrismaClientKnownRequestError`) carrying the original code and message, instead of an opaque failure, which keeps schema-drift-style problems debuggable ([#29512](https://github.com/prisma/prisma/pull/29512)).\r\n- The `prisma-client-js` generator no longer emits a stray `undefined` statement when generating from a schema that declares only enums or types and no models ([#29738](https://github.com/prisma/prisma/pull/29738), from [@kyungseopk1m](https://github.com/kyungseopk1m)).\r\n- Fixed a connection leak when an interactive transaction times out (`maxWait`) while it is still starting: the discarded transaction now sends an explicit `ROLLBACK` before the connection is returned to the pool, instead of releasing it mid-transaction. Previously, on adapters like `@prisma/adapter-pg` and `@prisma/adapter-neon`, the next query to reuse that connection could fail with `there is already a transaction in progress` — or silently commit the leaked transaction's work ([#29727](https://github.com/prisma/prisma/pull/29727), from [@lazerg](https://github.com/lazerg)).\r\n\r\n**CLI**\r\n\r\n- `prisma validate` (and other schema-loading commands) no longer hangs forever on a multi-file schema whose directories contain a symlink cycle, and no longer reports the same file twice when a directory is reachable under two spellings (e.g. `/tmp` → `/private/tmp` on macOS) ([#29740](https://github.com/prisma/prisma/pull/29740), from [@kyungseopk1m](https://github.com/kyungseopk1m)).\r\n- On Windows, engine binaries are now cached in a stable, user-level directory (`%APPDATA%\\Prisma`) instead of a `cwd`-relative `node_modules\\.cache`, which eliminated duplicate cache directories and the bloated Serverless/Docker bundles they caused ([#29730](https://github.com/prisma/prisma/pull/29730), from [@santichausis](https://github.com/santichausis); closes #22574, #6670, #11577).\r\n\r\n**Driver Adapters**\r\n\r\n- **@prisma/adapter-pg**, **@prisma/adapter-neon**, **@prisma/adapter-ppg**: Reading a `Bytes` column no longer emits Node.js' `DEP0005` deprecation warning, thanks to an upstream `postgres-bytea` bump ([#29538](https://github.com/prisma/prisma/pull/29538), from [@kolia-zamnius](https://github.com/kolia-zamnius)).\r\n- **@prisma/adapter-ppg**: `ColumnNotFound` (`P2022`) errors now parse both quoted and unquoted PostgreSQL column names, including identifiers containing spaces, matching the fix previously applied to `adapter-pg` ([#29737](https://github.com/prisma/prisma/pull/29737), from [@kyungseopk1m](https://github.com/kyungseopk1m)).\r\n- **@prisma/adapter-mssql**: Setting a `Bytes?` (`@db.VarBinary`) field to `null` no longer fails with an implicit-conversion error; the adapter now sends the parameter typed as `VarBinary` instead of letting SQL Server default it to `nvarchar` ([#29630](https://github.com/prisma/prisma/pull/29630), from [@AnupamKumar-1](https://github.com/AnupamKumar-1)).\r\n\r\n**Schema Engine**\r\n\r\n- `prisma migrate status` now reports a rolled-back migration that still exists on disk as *unapplied*, instead of incorrectly treating the schema as up to date ([prisma/prisma-engines#5817](https://github.com/prisma/prisma-engines/pull/5817), from [@goutamadwant](https://github.com/goutamadwant)).\r\n- Primary-key constraint renames are now rendered as separate `ALTER TABLE` statements on PostgreSQL, avoiding a database error when a single table has multiple changes in one migration ([prisma/prisma-engines#4906](https://github.com/prisma/prisma-engines/pull/4906), from [@eruditmorina](https://github.com/eruditmorina)).\r\n\r\n### Security\r\n\r\n- Resolved the `hono` security advisories at their source: `@prisma/dev` was updated to a version that no longer depends on `hono` at all, so the CLI is no longer exposed to those advisories through that path. We also patched moderate-severity advisories in `ajv` and `uuid` across production dependencies ([#29514](https://github.com/prisma/prisma/pull/29514)).\r\n- Hardened the Prisma Platform credentials file (`~/.config/prisma-platform/auth.json`) and its directory to `0o600` / `0o700` so OAuth tokens are no longer world-readable, bringing Prisma in line with the GitHub, AWS, and Google Cloud CLIs ([#29568](https://github.com/prisma/prisma/pull/29568), from Jaeyoung Yun).\r\n- Bumped the `openssl` crate in the schema engine binaries from 0.10.74 to 0.10.81 ([prisma/prisma-engines#5815](https://github.com/prisma/prisma-engines/pull/5815)).\r\n\r\n## Prisma Studio\r\n\r\nThe bundled Prisma Studio moves from `0.27.3` to `0.33.0` ([#29720](https://github.com/prisma/prisma/pull/29720)), gathering up everything shipped in the Studio releases in between.\r\n\r\n### Migrations view\r\n\r\nStudio can now visualise your **migration history**. This view is powered by **[Prisma Next](https://www.prisma.io/docs/orm/next)** — the next major version of Prisma ORM, a full TypeScript rewrite (available now in [Early Access](https://www.prisma.io/docs/next/getting-started)) that keeps the schema-first workflow and model-first queries you know, but treats your schema as a versioned, inspectable **contract** instead of compiling it into a heavy generated client. Prisma Next records every migration and its contract snapshots in the database, and Studio reads them to draw the timeline and diff below. Databases managed with classic Prisma Migrate don't carry this ledger, so the view simply stays hidden there.\r\n\r\nWhen the connected database has a Prisma Next migration ledger, a **Migrations** entry appears in the sidebar: a newest-first timeline of every applied migration with its name, apply time, operation count, and compact chips summarizing what changed (`+2 models`, `~2 models +3 fields`, `+1 model`, …). Selecting a migration opens a visual, FigJam-style diff canvas — added, removed, and changed models as colour-coded cards (`NEW` / `UPDATED` / `UNCHANGED`) with per-field before → after details, enum cards, and relation edges — next to a SQL panel of the executed statements and a Prisma-schema line diff. Switching migrations morphs the canvas rather than rebuilding it.\r\n\r\n![The Studio Migrations view: walking a Prisma Next migration history, the diff canvas morphing between migrations](https://github.com/user-attachments/assets/2633b77a-b1d9-4c3f-b5c4-c10908f040d9)\r\n\r\n<!-- On publishing: drag wip/demos/prisma-studio-migrations.webp into the GitHub release editor so it becomes a user-attachments URL. -->\r\n\r\n### Prisma Streams browser\r\n\r\nStudio gains first-class support for Prisma Streams: a dedicated stream browser, live stream aggregations, stream diagnostics, routing-key browsing, and a WAL-history handoff straight from your tables, plus richer stream request observability with concise event-log and OpenTelemetry span summaries.\r\n\r\n### Working with SQL\r\n\r\n- SQL execution, linting, and navigation are now **schema-aware**: unqualified identifiers resolve against the schema you've selected instead of always falling back to the adapter's default schema.\r\n- SQL result visualizations are rendered with Studio-owned chart configuration, and there's an optional **Queries** view backed by query-insights snapshots.\r\n- Added copy actions to the Query Details view.\r\n\r\n### Fixes\r\n\r\n- Fixed editing PostgreSQL text-array cells when queries are compiled with inline values.\r\n- Avoided cancelling and repeating introspection requests when Studio first mounts, removing duplicate startup work.\r\n\r\n## Thanks to our contributors\r\n\r\nA heartfelt thank you to the community members whose contributions shaped this release:\r\n\r\n[@AmirSa12](https://github.com/AmirSa12), [@kyungseopk1m](https://github.com/kyungseopk1m), [@nfl1ryxditimo12](https://github.com/nfl1ryxditimo12), [@jibin7jose](https://github.com/jibin7jose), [@santichausis](https://github.com/santichausis), [@kolia-zamnius](https://github.com/kolia-zamnius), [@goutamadwant](https://github.com/goutamadwant), [@eruditmorina](https://github.com/eruditmorina), [@lazerg](https://github.com/lazerg), [@AnupamKumar-1](https://github.com/AnupamKumar-1), [@Swapanrishi](https://github.com/Swapanrishi), [@anupamme](https://github.com/anupamme), and [@oyi77](https://github.com/oyi77).\r\n\r\n## Prisma Compute is now in public beta\r\n\r\n**\"Push code, it runs.\"** [Prisma Compute](https://www.prisma.io/compute) — managed hosting for TypeScript apps that run right next to your database — is now available in [public beta](https://blog.prisma.io/blog/launching-prisma-compute-public-beta), and free to use while the beta lasts.\r\n\r\nCompute deploys your app as a long-lived process on Bun, colocated with your Prisma Postgres database, so there are no cold starts, no request timeouts, and no separate hosting vendor to wire up. It's a fit for REST and GraphQL APIs, full-stack apps, streaming and gRPC, and the long-running, stateful AI agents that keep connections open and hold in-process caches — \"self-hosting, without the painful parts\".\r\n\r\n- **Push-to-deploy** from the CLI or via GitHub integration. Every deployment is an immutable, versioned release with its own preview URL, and rolling back is simply promoting a previous version.\r\n- **Branch-based environments** — each branch gets its own app and database, so you can preview a change before promoting it to production.\r\n- **Auto-wires with Prisma Postgres** (or bring any database), with automatic health checks and self-recovery.\r\n- **[Custom domains](https://blog.prisma.io/blog/prisma-compute-custom-domains)** — point a single CNAME at Prisma and Compute provisions and renews the TLS certificate for you, with no manual certificate uploads or private-key handling.\r\n\r\nWith Prisma ORM for type-safe data access, Prisma Postgres for the managed database, and now Prisma Compute for hosting, the whole stack lives in one place. Read the full story in the [Prisma Compute blog series](https://blog.prisma.io/blog/series/prisma-compute).\r\n\r\n## Enterprise support\r\n\r\nThousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.\r\n\r\nWith this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.","publishedAt":"2026-07-21T07:26:50.000Z","fetchedAt":"2026-08-26T10:01:54.633Z","url":"https://github.com/prisma/orm/releases/tag/7.9.0","media":[{"type":"image","url":"https://github.com/user-attachments/assets/8244a6dc-cdad-4028-a652-bb5ac6e4b271","alt":"prisma init scaffolds a project and installs the Prisma agent skills catalog","r2Key":"releases/70eee4f1c68cb253e5d475ff6772424e4004e073bf2461ec7386c87af088308a.webp","r2Url":"https://media.releases.sh/releases/70eee4f1c68cb253e5d475ff6772424e4004e073bf2461ec7386c87af088308a.webp"},{"type":"image","url":"https://github.com/user-attachments/assets/2633b77a-b1d9-4c3f-b5c4-c10908f040d9","alt":"The Studio Migrations view: walking a Prisma Next migration history, the diff canvas morphing between migrations","r2Key":"releases/fb38d8f40e91318b667415e3baf041e86554b69e94652d0154eaaec5bf9ed248.mp4","r2Url":"https://media.releases.sh/releases/fb38d8f40e91318b667415e3baf041e86554b69e94652d0154eaaec5bf9ed248.mp4"}],"coverageCount":0},{"id":"rel_vZv6YhuM-DtZ3lxuUUazm","version":"7.9.0","type":"feature","title":"7.9.0","summary":"Today, we are excited to share the 7.9.0 stable release 🎉 🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X! Highlights ORM Tab completions for the Prisma CLI Typing out CLI commands from memory is now optional. Prisma ships shell…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"Today, we are excited to share the `7.9.0` stable release 🎉\r\n\r\n**🌟 Star this repo for notifications about new releases, bug fixes & features — or [follow us on X](https://pris.ly/x)!**\r\n\r\n# Highlights\r\n\r\n## ORM\r\n\r\n### Tab completions for the Prisma CLI\r\n\r\nTyping out CLI commands from memory is now optional. Prisma ships **shell tab completions** for `bash`, `zsh`, `fish`, and PowerShell, covering commands, subcommands, options, flags, and even option values.\r\n\r\n**Setting it up.** Most projects run Prisma through a package manager, so completions are enabled through `@bomb.sh/tab`'s package-manager integration — install it once, then source the completion for your package manager and shell:\r\n\r\n```bash\r\n# 1. Install @bomb.sh/tab globally\r\nnpm install -g @bomb.sh/tab\r\n\r\n# 2. Wire up your package manager + shell (pnpm shown; swap in npm / yarn / bun):\r\necho 'source <(tab pnpm zsh)'  >> ~/.zshrc            # zsh\r\necho 'source <(tab pnpm bash)' >> ~/.bashrc           # bash\r\ntab pnpm fish > ~/.config/fish/completions/pnpm.fish  # fish\r\ntab pnpm powershell > ~/.tab-pnpm.ps1                 # PowerShell (then dot-source it from $PROFILE)\r\n```\r\n\r\n`@bomb.sh/tab` delegates to any locally-installed CLI that ships completions, so `pnpm prisma <TAB>`, `pnpm exec prisma <TAB>`, `yarn prisma <TAB>`, and `bun x prisma <TAB>` all complete Prisma's commands, options, and values — no per-project setup. (`npx` and `bunx` don't support completion themselves; use `npm exec` and `bun x`.)\r\n\r\nIf instead you have Prisma installed globally on your `PATH`, source its own completion directly: `source <(prisma complete zsh)` (or the `bash` / `fish` / `powershell` variant).\r\n\r\nThis is built on [`@bomb.sh/tab`](https://github.com/bombshell-dev/tab/), the same completion library that powers other CLIs in the ecosystem — including Cloudflare, Nuxt, and Vitest — so the package-manager completions you enable for Prisma work for those tools too. A wonderful community contribution from [@AmirSa12](https://github.com/AmirSa12) ([#28351](https://github.com/prisma/prisma/pull/28351)) — thank you!\r\n\r\nhttps://github.com/user-attachments/assets/1f916a60-ee4d-40be-bb7d-74035d48ca83\r\n\r\n### Prisma ORM, ready for AI agents\r\n\r\nCoding agents are now a first-class audience for Prisma, and 7.9.0 brings the first wave of work to make Prisma projects safe and productive for them to work in.\r\n\r\n**Agent skills installed with `prisma init`** ([#29689](https://github.com/prisma/prisma/pull/29689))\r\n\r\n`prisma init` now installs the [prisma/skills](https://github.com/prisma/skills) catalog into freshly scaffolded projects. Agents such as Claude Code, Cursor, Codex, and Windsurf start out with current, version-relevant Prisma knowledge instead of relying on whatever happened to be in their training data. The install is best-effort and never blocks scaffolding; opt out at any time with `--no-skills`.\r\n\r\n```terminal\r\nnpx prisma@latest init\r\n```\r\n\r\n![prisma init scaffolds a project and installs the Prisma agent skills catalog](https://github.com/user-attachments/assets/8244a6dc-cdad-4028-a652-bb5ac6e4b271)\r\n\r\n**A safer default around destructive commands** ([#29684](https://github.com/prisma/prisma/pull/29684), [#29691](https://github.com/prisma/prisma/pull/29691), [#29713](https://github.com/prisma/prisma/pull/29713))\r\n\r\nPrisma's AI safety checkpoint refuses to run destructive commands when it detects that an AI agent is at the keyboard, unless the user has given explicit consent. In this release we:\r\n\r\n- **Broadened agent detection** to cover today's landscape — Codex CLI (now on Linux as well as macOS), Qwen Code, GitHub Copilot CLI, OpenCode, Cline, Goose, Amp, Crush, Augment Code, Antigravity, Replit Agent, and Devin — plus generic `AI_AGENT` / `AGENT` conventions so future agents are caught without a code change.\r\n- **Extended the guard to `db push --accept-data-loss`**, which previously bypassed the checkpoint even though it can drop data.\r\n- **Removed the `migrate-reset` tool from the `prisma mcp` server** entirely — resetting a database drops it, and that is not an operation an agent should be handed as a first-class tool. An agent that needs a reset must run the CLI, where the checkpoint applies.\r\n\r\n### Bug Fixes\r\n\r\nMany of the fixes below are **community contributions** — thank you to everyone who reported and fixed these!\r\n\r\n**Prisma Client**\r\n\r\n- Fixed a severe TypeScript performance regression introduced in Prisma 7: restoring the `OmitOpts` generic default lets `tsc` reuse cached type instantiations again, bringing type-checking on large schemas back from minutes to seconds ([#29592](https://github.com/prisma/prisma/pull/29592), from [@nfl1ryxditimo12](https://github.com/nfl1ryxditimo12)).\r\n- The `XOR` type helper now rejects primitive values such as `data: 5`, which were previously accepted at compile time even though the runtime rejected them ([#29735](https://github.com/prisma/prisma/pull/29735), from [@kyungseopk1m](https://github.com/kyungseopk1m)).\r\n- `$queryRaw` and `$executeRaw` now fail fast with a clear validation error when passed an invalid `Date`, instead of silently serializing it as `null` and corrupting the value sent to the database ([#29697](https://github.com/prisma/prisma/pull/29697), from [@jibin7jose](https://github.com/jibin7jose)).\r\n- The generated client is no longer corrupted by a `///` documentation comment that contains a `*/` sequence; the comment terminator is now escaped when doc comments are emitted, in both the TypeScript and JavaScript generators ([#29736](https://github.com/prisma/prisma/pull/29736), from [@kyungseopk1m](https://github.com/kyungseopk1m)).\r\n- Improved the runtime and TypeScript error messages shown when a driver adapter is missing from the `PrismaClient` constructor; both now include a copy-pasteable example and a link to the [driver adapters docs](https://pris.ly/d/driver-adapters) ([#29624](https://github.com/prisma/prisma/pull/29624)).\r\n- Unmapped database errors from driver adapters now surface as a user-facing `P2039` (`PrismaClientKnownRequestError`) carrying the original code and message, instead of an opaque failure, which keeps schema-drift-style problems debuggable ([#29512](https://github.com/prisma/prisma/pull/29512)).\r\n- The `prisma-client-js` generator no longer emits a stray `undefined` statement when generating from a schema that declares only enums or types and no models ([#29738](https://github.com/prisma/prisma/pull/29738), from [@kyungseopk1m](https://github.com/kyungseopk1m)).\r\n- Fixed a connection leak when an interactive transaction times out (`maxWait`) while it is still starting: the discarded transaction now sends an explicit `ROLLBACK` before the connection is returned to the pool, instead of releasing it mid-transaction. Previously, on adapters like `@prisma/adapter-pg` and `@prisma/adapter-neon`, the next query to reuse that connection could fail with `there is already a transaction in progress` — or silently commit the leaked transaction's work ([#29727](https://github.com/prisma/prisma/pull/29727), from [@lazerg](https://github.com/lazerg)).\r\n\r\n**CLI**\r\n\r\n- `prisma validate` (and other schema-loading commands) no longer hangs forever on a multi-file schema whose directories contain a symlink cycle, and no longer reports the same file twice when a directory is reachable under two spellings (e.g. `/tmp` → `/private/tmp` on macOS) ([#29740](https://github.com/prisma/prisma/pull/29740), from [@kyungseopk1m](https://github.com/kyungseopk1m)).\r\n- On Windows, engine binaries are now cached in a stable, user-level directory (`%APPDATA%\\Prisma`) instead of a `cwd`-relative `node_modules\\.cache`, which eliminated duplicate cache directories and the bloated Serverless/Docker bundles they caused ([#29730](https://github.com/prisma/prisma/pull/29730), from [@santichausis](https://github.com/santichausis); closes #22574, #6670, #11577).\r\n\r\n**Driver Adapters**\r\n\r\n- **@prisma/adapter-pg**, **@prisma/adapter-neon**, **@prisma/adapter-ppg**: Reading a `Bytes` column no longer emits Node.js' `DEP0005` deprecation warning, thanks to an upstream `postgres-bytea` bump ([#29538](https://github.com/prisma/prisma/pull/29538), from [@kolia-zamnius](https://github.com/kolia-zamnius)).\r\n- **@prisma/adapter-ppg**: `ColumnNotFound` (`P2022`) errors now parse both quoted and unquoted PostgreSQL column names, including identifiers containing spaces, matching the fix previously applied to `adapter-pg` ([#29737](https://github.com/prisma/prisma/pull/29737), from [@kyungseopk1m](https://github.com/kyungseopk1m)).\r\n- **@prisma/adapter-mssql**: Setting a `Bytes?` (`@db.VarBinary`) field to `null` no longer fails with an implicit-conversion error; the adapter now sends the parameter typed as `VarBinary` instead of letting SQL Server default it to `nvarchar` ([#29630](https://github.com/prisma/prisma/pull/29630), from [@AnupamKumar-1](https://github.com/AnupamKumar-1)).\r\n\r\n**Schema Engine**\r\n\r\n- `prisma migrate status` now reports a rolled-back migration that still exists on disk as *unapplied*, instead of incorrectly treating the schema as up to date ([prisma/prisma-engines#5817](https://github.com/prisma/prisma-engines/pull/5817), from [@goutamadwant](https://github.com/goutamadwant)).\r\n- Primary-key constraint renames are now rendered as separate `ALTER TABLE` statements on PostgreSQL, avoiding a database error when a single table has multiple changes in one migration ([prisma/prisma-engines#4906](https://github.com/prisma/prisma-engines/pull/4906), from [@eruditmorina](https://github.com/eruditmorina)).\r\n\r\n### Security\r\n\r\n- Resolved the `hono` security advisories at their source: `@prisma/dev` was updated to a version that no longer depends on `hono` at all, so the CLI is no longer exposed to those advisories through that path. We also patched moderate-severity advisories in `ajv` and `uuid` across production dependencies ([#29514](https://github.com/prisma/prisma/pull/29514)).\r\n- Hardened the Prisma Platform credentials file (`~/.config/prisma-platform/auth.json`) and its directory to `0o600` / `0o700` so OAuth tokens are no longer world-readable, bringing Prisma in line with the GitHub, AWS, and Google Cloud CLIs ([#29568](https://github.com/prisma/prisma/pull/29568), from Jaeyoung Yun).\r\n- Bumped the `openssl` crate in the schema engine binaries from 0.10.74 to 0.10.81 ([prisma/prisma-engines#5815](https://github.com/prisma/prisma-engines/pull/5815)).\r\n\r\n## Prisma Studio\r\n\r\nThe bundled Prisma Studio moves from `0.27.3` to `0.33.0` ([#29720](https://github.com/prisma/prisma/pull/29720)), gathering up everything shipped in the Studio releases in between.\r\n\r\n### Migrations view\r\n\r\nStudio can now visualise your **migration history**. This view is powered by **[Prisma Next](https://www.prisma.io/docs/orm/next)** — the next major version of Prisma ORM, a full TypeScript rewrite (available now in [Early Access](https://www.prisma.io/docs/next/getting-started)) that keeps the schema-first workflow and model-first queries you know, but treats your schema as a versioned, inspectable **contract** instead of compiling it into a heavy generated client. Prisma Next records every migration and its contract snapshots in the database, and Studio reads them to draw the timeline and diff below. Databases managed with classic Prisma Migrate don't carry this ledger, so the view simply stays hidden there.\r\n\r\nWhen the connected database has a Prisma Next migration ledger, a **Migrations** entry appears in the sidebar: a newest-first timeline of every applied migration with its name, apply time, operation count, and compact chips summarizing what changed (`+2 models`, `~2 models +3 fields`, `+1 model`, …). Selecting a migration opens a visual, FigJam-style diff canvas — added, removed, and changed models as colour-coded cards (`NEW` / `UPDATED` / `UNCHANGED`) with per-field before → after details, enum cards, and relation edges — next to a SQL panel of the executed statements and a Prisma-schema line diff. Switching migrations morphs the canvas rather than rebuilding it.\r\n\r\n![The Studio Migrations view: walking a Prisma Next migration history, the diff canvas morphing between migrations](https://github.com/user-attachments/assets/2633b77a-b1d9-4c3f-b5c4-c10908f040d9)\r\n\r\n<!-- On publishing: drag wip/demos/prisma-studio-migrations.webp into the GitHub release editor so it becomes a user-attachments URL. -->\r\n\r\n### Prisma Streams browser\r\n\r\nStudio gains first-class support for Prisma Streams: a dedicated stream browser, live stream aggregations, stream diagnostics, routing-key browsing, and a WAL-history handoff straight from your tables, plus richer stream request observability with concise event-log and OpenTelemetry span summaries.\r\n\r\n### Working with SQL\r\n\r\n- SQL execution, linting, and navigation are now **schema-aware**: unqualified identifiers resolve against the schema you've selected instead of always falling back to the adapter's default schema.\r\n- SQL result visualizations are rendered with Studio-owned chart configuration, and there's an optional **Queries** view backed by query-insights snapshots.\r\n- Added copy actions to the Query Details view.\r\n\r\n### Fixes\r\n\r\n- Fixed editing PostgreSQL text-array cells when queries are compiled with inline values.\r\n- Avoided cancelling and repeating introspection requests when Studio first mounts, removing duplicate startup work.\r\n\r\n## Thanks to our contributors\r\n\r\nA heartfelt thank you to the community members whose contributions shaped this release:\r\n\r\n[@AmirSa12](https://github.com/AmirSa12), [@kyungseopk1m](https://github.com/kyungseopk1m), [@nfl1ryxditimo12](https://github.com/nfl1ryxditimo12), [@jibin7jose](https://github.com/jibin7jose), [@santichausis](https://github.com/santichausis), [@kolia-zamnius](https://github.com/kolia-zamnius), [@goutamadwant](https://github.com/goutamadwant), [@eruditmorina](https://github.com/eruditmorina), [@lazerg](https://github.com/lazerg), [@AnupamKumar-1](https://github.com/AnupamKumar-1), [@Swapanrishi](https://github.com/Swapanrishi), [@anupamme](https://github.com/anupamme), and [@oyi77](https://github.com/oyi77).\r\n\r\n## Prisma Compute is now in public beta\r\n\r\n**\"Push code, it runs.\"** [Prisma Compute](https://www.prisma.io/compute) — managed hosting for TypeScript apps that run right next to your database — is now available in [public beta](https://blog.prisma.io/blog/launching-prisma-compute-public-beta), and free to use while the beta lasts.\r\n\r\nCompute deploys your app as a long-lived process on Bun, colocated with your Prisma Postgres database, so there are no cold starts, no request timeouts, and no separate hosting vendor to wire up. It's a fit for REST and GraphQL APIs, full-stack apps, streaming and gRPC, and the long-running, stateful AI agents that keep connections open and hold in-process caches — \"self-hosting, without the painful parts\".\r\n\r\n- **Push-to-deploy** from the CLI or via GitHub integration. Every deployment is an immutable, versioned release with its own preview URL, and rolling back is simply promoting a previous version.\r\n- **Branch-based environments** — each branch gets its own app and database, so you can preview a change before promoting it to production.\r\n- **Auto-wires with Prisma Postgres** (or bring any database), with automatic health checks and self-recovery.\r\n- **[Custom domains](https://blog.prisma.io/blog/prisma-compute-custom-domains)** — point a single CNAME at Prisma and Compute provisions and renews the TLS certificate for you, with no manual certificate uploads or private-key handling.\r\n\r\nWith Prisma ORM for type-safe data access, Prisma Postgres for the managed database, and now Prisma Compute for hosting, the whole stack lives in one place. Read the full story in the [Prisma Compute blog series](https://blog.prisma.io/blog/series/prisma-compute).\r\n\r\n## Enterprise support\r\n\r\nThousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.\r\n\r\nWith this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.","publishedAt":"2026-07-21T07:26:50.000Z","fetchedAt":"2026-07-21T08:48:57.105Z","url":"https://github.com/prisma/prisma/releases/tag/7.9.0","media":[{"type":"image","url":"https://github.com/user-attachments/assets/8244a6dc-cdad-4028-a652-bb5ac6e4b271","alt":"prisma init scaffolds a project and installs the Prisma agent skills catalog","r2Key":"releases/70eee4f1c68cb253e5d475ff6772424e4004e073bf2461ec7386c87af088308a.webp","r2Url":"https://media.releases.sh/releases/70eee4f1c68cb253e5d475ff6772424e4004e073bf2461ec7386c87af088308a.webp"},{"type":"image","url":"https://github.com/user-attachments/assets/2633b77a-b1d9-4c3f-b5c4-c10908f040d9","alt":"The Studio Migrations view: walking a Prisma Next migration history, the diff canvas morphing between migrations","r2Key":"releases/fb38d8f40e91318b667415e3baf041e86554b69e94652d0154eaaec5bf9ed248.mp4","r2Url":"https://media.releases.sh/releases/fb38d8f40e91318b667415e3baf041e86554b69e94652d0154eaaec5bf9ed248.mp4"}],"coverageCount":0},{"id":"rel_CmxQwQY7EhEEVWhINTalk","version":"7.8.0","type":"feature","title":"7.8.0","summary":"Today, we are excited to share the 7.8.0 stable release 🎉 🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X! Highlights ORM Features Prisma Client Added a queryPlanCacheMaxSize option to the PrismaClient constructor for…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"Today, we are excited to share the `7.8.0` stable release 🎉\r\n\r\n**🌟 Star this repo for notifications about new releases, bug fixes & features — or [follow us on X](https://pris.ly/x)!**\r\n\r\n# Highlights\r\n\r\n## ORM\r\n\r\n### Features\r\n\r\n**Prisma Client**\r\n\r\n- Added a `queryPlanCacheMaxSize` option to the `PrismaClient` constructor for fine-grained control over the query plan cache. Pass `0` to disable the cache entirely, or omit it to use the default cache size. A larger value can improve performance in applications that execute many unique queries, while a smaller one can reduce memory usage. (#29503)\r\n\r\n### Bug Fixes\r\n\r\n**Prisma Client**\r\n\r\n- Fixed an equality filter panic and incorrect `::jsonb` cast when filtering on PostgreSQL JSON list columns. Queries using `where: { jsonListField: { equals: [...] } }` no longer panic with a type mismatch or emit invalid SQL. (prisma/prisma-engines#5804)\r\n- Fixed case-insensitive JSON field filtering (`mode: insensitive`), allowing `where: { jsonField: { equals: \"...\", mode: \"insensitive\" } }` to work correctly. (prisma/prisma-engines#5806)\r\n- Fixed incorrect parameterization of enum values that have a custom database name set via `@map`. (#29422)\r\n- Fixed a database parameter limit check (`P2029`), which could incorrectly reject or miss over-limit queries. (#29422)\r\n- Fixed a regression that caused missing SQL Server `VARCHAR` casts for parameterized values. (prisma/prisma-engines#5801)\r\n\r\nSchema Engine\r\n\r\n- Fixed a misleading error message in `prisma migrate diff` that referenced the `--shadow-database-url` CLI flag, which was removed in Prisma 7. (#29455)\r\n- Fixed `prisma migrate dev` (and shadow database migration replay in general) failing with `CREATE INDEX CONCURRENTLY cannot run inside a transaction block` when a migration contained concurrent index creation statements on PostgreSQL. (prisma/prisma-engines#5799)\r\n- Fixed PostgreSQL introspection silently dropping sequence defaults when the database returns the schema-qualified form `pg_catalog.nextval('sequence_name'::regclass)` instead of the bare `nextval(...)`. Columns backed by sequences now correctly appear as `@default(autoincrement())` in the Prisma schema in all cases. (prisma/prisma-engines#5802)\r\n\r\n**Driver Adapters**\r\n\r\n- **@prisma/adapter-d1**: Savepoint operations (`createSavepoint`, `rollbackToSavepoint`, `releaseSavepoint`) now silently no-op with debug logging instead of executing SQL statements, consistent with how the D1 adapter already treats top-level transactions. (#29499)\r\n\r\n## Open roles at Prisma\r\n\r\nInterested in joining Prisma? We're growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [Careers page](https://www.prisma.io/careers#current) and find the role that's right for you.\r\n\r\n## Enterprise support\r\n\r\nThousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.\r\n\r\nWith this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.","publishedAt":"2026-04-22T14:19:23.000Z","fetchedAt":"2026-08-26T10:01:54.633Z","url":"https://github.com/prisma/orm/releases/tag/7.8.0","media":[],"coverageCount":0},{"id":"rel_PjJs5gJMl6nnS7ZCGAwbK","version":"7.8.0","type":"feature","title":"7.8.0","summary":"Today, we are excited to share the 7.8.0 stable release 🎉 🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X! Highlights ORM Features Prisma Client Added a queryPlanCacheMaxSize option to the PrismaClient constructor for…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"Today, we are excited to share the `7.8.0` stable release 🎉\r\n\r\n**🌟 Star this repo for notifications about new releases, bug fixes & features — or [follow us on X](https://pris.ly/x)!**\r\n\r\n# Highlights\r\n\r\n## ORM\r\n\r\n### Features\r\n\r\n**Prisma Client**\r\n\r\n- Added a `queryPlanCacheMaxSize` option to the `PrismaClient` constructor for fine-grained control over the query plan cache. Pass `0` to disable the cache entirely, or omit it to use the default cache size. A larger value can improve performance in applications that execute many unique queries, while a smaller one can reduce memory usage. (#29503)\r\n\r\n### Bug Fixes\r\n\r\n**Prisma Client**\r\n\r\n- Fixed an equality filter panic and incorrect `::jsonb` cast when filtering on PostgreSQL JSON list columns. Queries using `where: { jsonListField: { equals: [...] } }` no longer panic with a type mismatch or emit invalid SQL. (prisma/prisma-engines#5804)\r\n- Fixed case-insensitive JSON field filtering (`mode: insensitive`), allowing `where: { jsonField: { equals: \"...\", mode: \"insensitive\" } }` to work correctly. (prisma/prisma-engines#5806)\r\n- Fixed incorrect parameterization of enum values that have a custom database name set via `@map`. (#29422)\r\n- Fixed a database parameter limit check (`P2029`), which could incorrectly reject or miss over-limit queries. (#29422)\r\n- Fixed a regression that caused missing SQL Server `VARCHAR` casts for parameterized values. (prisma/prisma-engines#5801)\r\n\r\nSchema Engine\r\n\r\n- Fixed a misleading error message in `prisma migrate diff` that referenced the `--shadow-database-url` CLI flag, which was removed in Prisma 7. (#29455)\r\n- Fixed `prisma migrate dev` (and shadow database migration replay in general) failing with `CREATE INDEX CONCURRENTLY cannot run inside a transaction block` when a migration contained concurrent index creation statements on PostgreSQL. (prisma/prisma-engines#5799)\r\n- Fixed PostgreSQL introspection silently dropping sequence defaults when the database returns the schema-qualified form `pg_catalog.nextval('sequence_name'::regclass)` instead of the bare `nextval(...)`. Columns backed by sequences now correctly appear as `@default(autoincrement())` in the Prisma schema in all cases. (prisma/prisma-engines#5802)\r\n\r\n**Driver Adapters**\r\n\r\n- **@prisma/adapter-d1**: Savepoint operations (`createSavepoint`, `rollbackToSavepoint`, `releaseSavepoint`) now silently no-op with debug logging instead of executing SQL statements, consistent with how the D1 adapter already treats top-level transactions. (#29499)\r\n\r\n## Open roles at Prisma\r\n\r\nInterested in joining Prisma? We're growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [Careers page](https://www.prisma.io/careers#current) and find the role that's right for you.\r\n\r\n## Enterprise support\r\n\r\nThousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.\r\n\r\nWith this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.","publishedAt":"2026-04-22T14:19:23.000Z","fetchedAt":"2026-04-22T15:01:41.604Z","url":"https://github.com/prisma/prisma/releases/tag/7.8.0","media":[],"coverageCount":0},{"id":"rel_NUdTRg6riOffKGoIiOX1D","version":"7.7.0","type":"feature","title":"7.7.0","summary":"Today, we are excited to share the 7.7.0 stable release 🎉 🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X! Highlights ORM prisma bootstrap command A new prisma bootstrap command (#29374, #29424) sequences the full Prisma…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"Today, we are excited to share the `7.7.0` stable release 🎉\r\n\r\n**🌟 Star this repo for notifications about new releases, bug fixes & features — or [follow us on X](https://pris.ly/x)!**\r\n\r\n# Highlights\r\n\r\n## ORM\r\n\r\n### `prisma bootstrap` command\r\n\r\nA new `prisma bootstrap` command ([#29374](https://github.com/prisma/prisma/pull/29374), [#29424](https://github.com/prisma/prisma/pull/29424)) sequences the full [Prisma Postgres](https://prisma.io/postgres) setup into a single interactive flow. It detects the current project state and runs only the steps that are needed:\r\n\r\n1. **Init or scaffold** — In an empty directory, offers a choice of 10 starter templates (Next.js, Express, Hono, Fastify, Nuxt, SvelteKit, Remix, React Router 7, Astro, NestJS) from [prisma-examples](https://github.com/prisma/prisma-examples). In an existing project without a schema, runs `prisma init`.\r\n2. **Link** — Authenticates via the browser and connects to a Prisma Postgres database. Skips if already linked.\r\n3. **Install dependencies** — Detects the package manager and offers to install missing `@prisma/client`, `prisma`, and `dotenv`.\r\n4. **Migrate** — Runs `prisma migrate dev` if the schema contains models.\r\n5. **Generate** — Runs `prisma generate`.\r\n6. **Seed** — Runs `prisma db seed` if a seed script is configured.\r\n\r\nEach side-effecting step prompts for confirmation. Re-running the command skips already-completed steps.\r\n\r\n**Basic usage**\r\n\r\n```terminal\r\nnpx prisma@latest bootstrap\r\n```\r\n\r\n**With a starter template**\r\n\r\n```terminal\r\nnpx prisma@latest bootstrap --template nextjs\r\n```\r\n\r\n**Non-interactive (CI)**\r\n\r\n```terminal\r\nnpx prisma@latest bootstrap --api-key \"$PRISMA_API_KEY\" --database \"db_abc123\"\r\n```\r\n\r\n## Open roles at Prisma\r\n\r\nInterested in joining Prisma? We're growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [Careers page](https://www.prisma.io/careers#current) and find the role that's right for you.\r\n\r\n## Enterprise support\r\n\r\nThousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.\r\n\r\nWith this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.","publishedAt":"2026-04-07T16:00:33.000Z","fetchedAt":"2026-08-26T10:01:54.633Z","url":"https://github.com/prisma/orm/releases/tag/7.7.0","media":[],"coverageCount":0},{"id":"rel_2rJS7vVgTAdbR326O1C6Z","version":"7.7.0","type":"feature","title":"7.7.0","summary":"Today, we are excited to share the 7.7.0 stable release 🎉 🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X! Highlights ORM prisma bootstrap command A new prisma bootstrap command (#29374, #29424) sequences the full Prisma…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"Today, we are excited to share the `7.7.0` stable release 🎉\r\n\r\n**🌟 Star this repo for notifications about new releases, bug fixes & features — or [follow us on X](https://pris.ly/x)!**\r\n\r\n# Highlights\r\n\r\n## ORM\r\n\r\n### `prisma bootstrap` command\r\n\r\nA new `prisma bootstrap` command ([#29374](https://github.com/prisma/prisma/pull/29374), [#29424](https://github.com/prisma/prisma/pull/29424)) sequences the full [Prisma Postgres](https://prisma.io/postgres) setup into a single interactive flow. It detects the current project state and runs only the steps that are needed:\r\n\r\n1. **Init or scaffold** — In an empty directory, offers a choice of 10 starter templates (Next.js, Express, Hono, Fastify, Nuxt, SvelteKit, Remix, React Router 7, Astro, NestJS) from [prisma-examples](https://github.com/prisma/prisma-examples). In an existing project without a schema, runs `prisma init`.\r\n2. **Link** — Authenticates via the browser and connects to a Prisma Postgres database. Skips if already linked.\r\n3. **Install dependencies** — Detects the package manager and offers to install missing `@prisma/client`, `prisma`, and `dotenv`.\r\n4. **Migrate** — Runs `prisma migrate dev` if the schema contains models.\r\n5. **Generate** — Runs `prisma generate`.\r\n6. **Seed** — Runs `prisma db seed` if a seed script is configured.\r\n\r\nEach side-effecting step prompts for confirmation. Re-running the command skips already-completed steps.\r\n\r\n**Basic usage**\r\n\r\n```terminal\r\nnpx prisma@latest bootstrap\r\n```\r\n\r\n**With a starter template**\r\n\r\n```terminal\r\nnpx prisma@latest bootstrap --template nextjs\r\n```\r\n\r\n**Non-interactive (CI)**\r\n\r\n```terminal\r\nnpx prisma@latest bootstrap --api-key \"$PRISMA_API_KEY\" --database \"db_abc123\"\r\n```\r\n\r\n## Open roles at Prisma\r\n\r\nInterested in joining Prisma? We're growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [Careers page](https://www.prisma.io/careers#current) and find the role that's right for you.\r\n\r\n## Enterprise support\r\n\r\nThousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.\r\n\r\nWith this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.","publishedAt":"2026-04-07T16:00:33.000Z","fetchedAt":"2026-04-07T20:01:01.145Z","url":"https://github.com/prisma/prisma/releases/tag/7.7.0","media":[],"coverageCount":0},{"id":"rel_vcLx2j4LavLdUdeO_Yk--","version":"6.19.3","type":"feature","title":"6.19.3","summary":"Today, we are issuing a 6.19.3 patch release in the Prisma 6 release line. It updates the effect dependency to resolve a security vulnerability. Changes: https://github.com/prisma/prisma/pull/29416","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"Today, we are issuing a 6.19.3 patch release in the Prisma 6 release line. It updates the `effect` dependency to resolve a security vulnerability.\r\n\r\nChanges:\r\nhttps://github.com/prisma/prisma/pull/29416","publishedAt":"2026-04-01T11:23:29.000Z","fetchedAt":"2026-08-26T10:01:54.633Z","url":"https://github.com/prisma/orm/releases/tag/6.19.3","media":[],"coverageCount":0},{"id":"rel_XERy91Nd13d8twFydwcw7","version":"6.19.3","type":"feature","title":"6.19.3","summary":"Today, we are issuing a 6.19.3 patch release in the Prisma 6 release line. It updates the effect dependency to resolve a security vulnerability. Changes: https://github.com/prisma/prisma/pull/29416","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"Today, we are issuing a 6.19.3 patch release in the Prisma 6 release line. It updates the `effect` dependency to resolve a security vulnerability.\r\n\r\nChanges:\r\nhttps://github.com/prisma/prisma/pull/29416","publishedAt":"2026-04-01T11:23:29.000Z","fetchedAt":"2026-04-03T19:01:04.690Z","url":"https://github.com/prisma/prisma/releases/tag/6.19.3","media":[],"coverageCount":0},{"id":"rel_0PcqHMwZFhpT85kSuOKYb","version":"7.6.0","type":"feature","title":"7.6.0","summary":"Today, we are excited to share the 7.6.0 stable release 🎉 🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X! Highlights ORM Features CLI Added a prisma postgres link command that connects a local project to a Prisma Postgres…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"Today, we are excited to share the `7.6.0` stable release 🎉\r\n\r\n**🌟 Star this repo for notifications about new releases, bug fixes & features — or [follow us on X](https://pris.ly/x)!**\r\n\r\n# Highlights\r\n\r\n## ORM\r\n\r\n### Features\r\n\r\n**CLI**\r\n\r\n- Added a `prisma postgres link` command that connects a local project to a Prisma Postgres database. This is the first command in a new `prisma postgres` command group for managing Prisma Postgres databases directly from the CLI. (#29352)\r\n\r\n**Driver Adapters**\r\n\r\n- **@prisma/adapter-pg**: Added a `statementNameGenerator` option that accepts a custom prepared statement name generator to allow users to leverage `pg` statement caching (#29395)\r\n- **@prisma/adapter-pg**: Added support for usage of connection strings directly in the constructor for improved ergonomics (#29287)\r\n- **@prisma/adapter-mariadb**: Added a `useTextProtocol` option in the constructor to toggle between text and binary protocols (#29392)\r\n\r\n### **Bug Fixes**\r\n\r\n**Prisma Client**\r\n\r\n- Disabled caching of `createMany` queries to avoid cache bloat and potential Node.js crashes in bulk operations (#29382)\r\n- Made `NowGenerator` lazy to avoid synchronous `new Date()` calls, fixing Next.js \"dynamic usage\" errors in cached components (#28724)\r\n- Fixed missing export of `Get<Model>GroupByPayload` type in the new `prisma-client` generator, making it accessible for TypeScript usage (#29346)\r\n\r\n**CLI**\r\n\r\n- Added streaming parsing with automatic fallback to handle Prisma schemas that produce extremely large intermediate strings (>500MB) that hit V8's string limits (#29377)\r\n\r\n**Driver Adapters**\r\n\r\n- **@prisma/adapter-pg**: Relaxed the `@types/pg` version constraint to `^8.16.0` for compatibility with newer PostgreSQL type definitions (#29390)\r\n- **@prisma/adapter-pg**: Corrected error handling for `ColumnNotFound` errors to correctly extract column names from both quoted and unquoted PostgreSQL error messages (#29307)\r\n- **@prisma/adapter-mariadb**: Modified the adapter to disable `mariadb` statement caching by default to address a reported leak (#29392)\r\n\r\n## Prisma Studio\r\n\r\nWe’re continuing our work to improve Prisma Studio with more features being added. \r\n\r\n**Dark Mode**\r\n\r\nNeed we say more? You’ve all asked for it, and it’s back. \r\n\r\nhttps://github.com/user-attachments/assets/214149dd-5dd3-4295-9fa3-0da3f8d28197\r\n \r\n\r\n**Copy as markdown**\r\n\r\nNow, you can copy one or more rows as either CSV or Markdown\r\n\r\n<img width=\"1888\" height=\"672\" alt=\"CleanShot 2026-03-11 at 16 04 09@2x\" src=\"https://github.com/user-attachments/assets/402b4c77-08ac-4c2d-b61a-0135eb42a9af\" />\r\n\r\n\r\n\r\n**Multi-cell editing**\r\n\r\nThis is big one, something that folks have been asking for. Now, it’s possible to edit multiple cells while inspecting your database. If you make any changes, you’ll be prompted to either save or discard them. This makes manually adding new rows much easier to accomplish.\r\n\r\n**Back relations**\r\n\r\nIf your data references another table, Prisma Studio now links to the related records, making it easy to inspect them. This makes traversing your database much simpler.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/4977a926-413b-495f-b651-b7554eefea04\r\n\r\n\r\n\r\n**Generative SQL with AI**\r\n\r\nIf you need to inspect your database, instead of manually writing the SQL you may need, you can use natural language and AI to generate the appropriate SQL statements. \r\n\r\n\r\nhttps://github.com/user-attachments/assets/e57c0afb-c3ed-471b-b55a-42395a134863\r\n\r\n\r\n\r\n## Open roles at Prisma\r\n\r\nInterested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [Careers page](https://www.prisma.io/careers#current) and find the role that’s right for you. \r\n\r\n## Enterprise support\r\n\r\nThousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.\r\n\r\nWith this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.\r\n","publishedAt":"2026-03-27T14:11:00.000Z","fetchedAt":"2026-08-26T10:01:54.972Z","url":"https://github.com/prisma/orm/releases/tag/7.6.0","media":[{"type":"image","url":"https://github.com/user-attachments/assets/402b4c77-08ac-4c2d-b61a-0135eb42a9af","r2Key":"releases/ef83e90e480278b0ef33a4a734ad68943baf481441e1b17c72efeca77213286e.png","r2Url":"https://media.releases.sh/releases/ef83e90e480278b0ef33a4a734ad68943baf481441e1b17c72efeca77213286e.png"}],"coverageCount":0},{"id":"rel_Vrd8Fp1G4lrcFdOD-o7RP","version":"7.6.0","type":"feature","title":"7.6.0","summary":"Today, we are excited to share the 7.6.0 stable release 🎉 🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X! Highlights ORM Features CLI Added a prisma postgres link command that connects a local project to a Prisma Postgres…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"Today, we are excited to share the `7.6.0` stable release 🎉\r\n\r\n**🌟 Star this repo for notifications about new releases, bug fixes & features — or [follow us on X](https://pris.ly/x)!**\r\n\r\n# Highlights\r\n\r\n## ORM\r\n\r\n### Features\r\n\r\n**CLI**\r\n\r\n- Added a `prisma postgres link` command that connects a local project to a Prisma Postgres database. This is the first command in a new `prisma postgres` command group for managing Prisma Postgres databases directly from the CLI. (#29352)\r\n\r\n**Driver Adapters**\r\n\r\n- **@prisma/adapter-pg**: Added a `statementNameGenerator` option that accepts a custom prepared statement name generator to allow users to leverage `pg` statement caching (#29395)\r\n- **@prisma/adapter-pg**: Added support for usage of connection strings directly in the constructor for improved ergonomics (#29287)\r\n- **@prisma/adapter-mariadb**: Added a `useTextProtocol` option in the constructor to toggle between text and binary protocols (#29392)\r\n\r\n### **Bug Fixes**\r\n\r\n**Prisma Client**\r\n\r\n- Disabled caching of `createMany` queries to avoid cache bloat and potential Node.js crashes in bulk operations (#29382)\r\n- Made `NowGenerator` lazy to avoid synchronous `new Date()` calls, fixing Next.js \"dynamic usage\" errors in cached components (#28724)\r\n- Fixed missing export of `Get<Model>GroupByPayload` type in the new `prisma-client` generator, making it accessible for TypeScript usage (#29346)\r\n\r\n**CLI**\r\n\r\n- Added streaming parsing with automatic fallback to handle Prisma schemas that produce extremely large intermediate strings (>500MB) that hit V8's string limits (#29377)\r\n\r\n**Driver Adapters**\r\n\r\n- **@prisma/adapter-pg**: Relaxed the `@types/pg` version constraint to `^8.16.0` for compatibility with newer PostgreSQL type definitions (#29390)\r\n- **@prisma/adapter-pg**: Corrected error handling for `ColumnNotFound` errors to correctly extract column names from both quoted and unquoted PostgreSQL error messages (#29307)\r\n- **@prisma/adapter-mariadb**: Modified the adapter to disable `mariadb` statement caching by default to address a reported leak (#29392)\r\n\r\n## Prisma Studio\r\n\r\nWe’re continuing our work to improve Prisma Studio with more features being added. \r\n\r\n**Dark Mode**\r\n\r\nNeed we say more? You’ve all asked for it, and it’s back. \r\n\r\nhttps://github.com/user-attachments/assets/214149dd-5dd3-4295-9fa3-0da3f8d28197\r\n \r\n\r\n**Copy as markdown**\r\n\r\nNow, you can copy one or more rows as either CSV or Markdown\r\n\r\n<img width=\"1888\" height=\"672\" alt=\"CleanShot 2026-03-11 at 16 04 09@2x\" src=\"https://github.com/user-attachments/assets/402b4c77-08ac-4c2d-b61a-0135eb42a9af\" />\r\n\r\n\r\n\r\n**Multi-cell editing**\r\n\r\nThis is big one, something that folks have been asking for. Now, it’s possible to edit multiple cells while inspecting your database. If you make any changes, you’ll be prompted to either save or discard them. This makes manually adding new rows much easier to accomplish.\r\n\r\n**Back relations**\r\n\r\nIf your data references another table, Prisma Studio now links to the related records, making it easy to inspect them. This makes traversing your database much simpler.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/4977a926-413b-495f-b651-b7554eefea04\r\n\r\n\r\n\r\n**Generative SQL with AI**\r\n\r\nIf you need to inspect your database, instead of manually writing the SQL you may need, you can use natural language and AI to generate the appropriate SQL statements. \r\n\r\n\r\nhttps://github.com/user-attachments/assets/e57c0afb-c3ed-471b-b55a-42395a134863\r\n\r\n\r\n\r\n## Open roles at Prisma\r\n\r\nInterested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [Careers page](https://www.prisma.io/careers#current) and find the role that’s right for you. \r\n\r\n## Enterprise support\r\n\r\nThousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.\r\n\r\nWith this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.\r\n","publishedAt":"2026-03-27T14:11:00.000Z","fetchedAt":"2026-03-31T14:07:51.751Z","url":"https://github.com/prisma/prisma/releases/tag/7.6.0","media":[],"coverageCount":0},{"id":"rel_e2GdCm9zXb26n6AyMOUSH","version":"7.5.0","type":"feature","title":"7.5.0","summary":"Today, we are excited to share the 7.5.0 stable release 🎉 🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X! Highlights ORM Features Added support for nested transaction rollbacks via savepoints (#21678) Adds support for nested…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"Today, we are excited to share the `7.5.0` stable release 🎉\r\n\r\n**🌟 Star this repo for notifications about new releases, bug fixes & features — or [follow us on X](https://pris.ly/x)!**\r\n\r\n\r\n# Highlights\r\n\r\n## ORM\r\n\r\n### Features\r\n\r\n- **Added support for nested transaction rollbacks via savepoints (**[#21678](https://github.com/prisma/prisma/pull/21678))\r\n    \r\n    Adds support for **nested transaction rollback behavior** for SQL databases: if an outer transaction fails, the inner nested transaction is rolled back as well. Implements this by tracking **transaction ID + nesting depth** so Prisma can reuse an existing open transaction in the underlying engine, and it also enables using **`$transaction` from an interactive transaction client**.\r\n    \r\n\r\n### Bug fixes\r\n\r\n**Driver Adapters**\r\n\r\n- Made the  `adapter-mariadb` use the binary MySQL protocol to fix an issue with lossy number conversions ([#29285](https://github.com/prisma/prisma/pull/29285))\r\n- Made `@types/pg` a direct dependency of `adapter-pg` for better TypeScript experience out-of-the-box ([#29277](https://github.com/prisma/prisma/pull/29277))\r\n\r\n**Prisma Client**\r\n\r\n- Resolved `Prisma.DbNull` serializing as empty object in some bundled environments like Next.js ([#29286](https://github.com/prisma/prisma/pull/29286))\r\n- Fixed DateTime fields returning `Invalid Date` with `unixepoch-ms` timestamps in some cases ([#29274](https://github.com/prisma/prisma/pull/29274))\r\n- Fixed a cursor-based pagination issue with `@db.Date` columns ([#29327](https://github.com/prisma/prisma/pull/29327))\r\n\r\n**Schema Engine**\r\n\r\n- Manual partial indexes are now preserved when `partialIndexes` preview feature is disabled, preventing unnecessary drops and additions in migrations ([#5790](https://github.com/prisma/prisma-engines/pull/5790), [#5795](https://github.com/prisma/prisma-engines/pull/5795))\r\n- Enhanced partial index predicate comparison to handle quoted vs unquoted identifiers correctly, eliminating needless recreate cycles ([#5788](https://github.com/prisma/prisma-engines/pull/5788))\r\n- Excluded partial unique indexes from DMMF `uniqueFields` and `uniqueIndexes` to prevent incorrect `findUnique` input type generation ([#5792](https://github.com/prisma/prisma-engines/pull/5792))\r\n\r\n\r\n\r\n## Studio\r\n\r\nWith the launch of Prisma ORM v7, we also introduced a rebuilt version of Prisma Studio. With the feedback we’ve gathered since the release, we’ve added some high requested features to help make Studio a better experience.\r\n\r\n**Multi-cell Selection & Full Table Search**\r\n\r\nThis release brings the ability to select multiple cells when viewing your database. In addition to being able to select multiple cells, you can also search across your database. You can search for a specific table or for specific cells within that table. \r\n\r\n![Adobe Express - CleanShot 2026-03-04 at 21 15 08-2](https://github.com/user-attachments/assets/e3d2aa3d-ae03-47f0-a5d6-3530675864f7)\r\n\r\n\r\n**More intuitive filtering**\r\n\r\nFiltering is now easier to use, and includes an option for raw SQL filters.\r\n\r\n![CleanShot 2026-03-11 at 11 26 35](https://github.com/user-attachments/assets/ba20f670-3770-4dcf-869f-673519bd847c)\r\n\r\n\r\nAnd if you are using Studio in Console, you can use ai generated filters:\r\n![CleanShot 2026-03-11 at 11 28 18](https://github.com/user-attachments/assets/4bd1c328-2429-4fb1-948d-d8d841900f22)\r\n\r\n\r\n\r\n**Cmd+k Command Palette**\r\n\r\nYou can now use the keyboard to perform most actions in Studio with the new cmd+k command palette\r\n![CleanShot 2026-03-11 at 11 30 35](https://github.com/user-attachments/assets/691b7a6e-c677-480c-addc-db42fc2aa9a5)\r\n\r\n\r\n\r\n**Run raw SQL queries**\r\n\r\nAnother feature we’ve included in Prisma Studio is the ability to run raw SQL queries against your data. There’s a new “SQL” tab in the sidebar that will bring you to page where you can perform any queries against your data. Below, we’re getting all the rows in the “Todo” table. \r\n\r\n![Adobe Express - Screen Recording 2026-03-10 at 2 30 52 PM-2](https://github.com/user-attachments/assets/9f3cf91f-23d3-49f1-9cd7-661752186432)\r\n\r\n\r\n## Open roles at Prisma\r\n\r\nInterested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [[Careers page](https://www.prisma.io/careers#current)](https://www.prisma.io/careers#current) and find the role that’s right for you. \r\n\r\n## Enterprise support\r\n\r\nThousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.\r\n\r\nWith this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.","publishedAt":"2026-03-11T14:57:08.000Z","fetchedAt":"2026-08-26T10:01:54.972Z","url":"https://github.com/prisma/orm/releases/tag/7.5.0","media":[{"type":"image","url":"https://github.com/user-attachments/assets/e3d2aa3d-ae03-47f0-a5d6-3530675864f7","alt":"Adobe Express - CleanShot 2026-03-04 at 21 15 08-2","r2Key":"releases/78433da901ecac61bbd9afffe396abf366611d7e6bc005821cdf010d4b833997.mp4","r2Url":"https://media.releases.sh/releases/78433da901ecac61bbd9afffe396abf366611d7e6bc005821cdf010d4b833997.mp4"},{"type":"image","url":"https://github.com/user-attachments/assets/ba20f670-3770-4dcf-869f-673519bd847c","alt":"CleanShot 2026-03-11 at 11 26 35","r2Key":"releases/b81f7220837b891620f9fc0d0758a6e386729c6f6dc4a2737bdb372678279658.mp4","r2Url":"https://media.releases.sh/releases/b81f7220837b891620f9fc0d0758a6e386729c6f6dc4a2737bdb372678279658.mp4"},{"type":"image","url":"https://github.com/user-attachments/assets/4bd1c328-2429-4fb1-948d-d8d841900f22","alt":"CleanShot 2026-03-11 at 11 28 18","r2Key":"releases/f5f56df22799a7543750c41bbc7620c27cd800c264747dfab94341e801503d31.mp4","r2Url":"https://media.releases.sh/releases/f5f56df22799a7543750c41bbc7620c27cd800c264747dfab94341e801503d31.mp4"},{"type":"image","url":"https://github.com/user-attachments/assets/691b7a6e-c677-480c-addc-db42fc2aa9a5","alt":"CleanShot 2026-03-11 at 11 30 35","r2Key":"releases/e9e64dcf5dff1acd4e421c775f1b42d2306f84dbcbaed37ede7ce4132234bb38.mp4","r2Url":"https://media.releases.sh/releases/e9e64dcf5dff1acd4e421c775f1b42d2306f84dbcbaed37ede7ce4132234bb38.mp4"},{"type":"image","url":"https://github.com/user-attachments/assets/9f3cf91f-23d3-49f1-9cd7-661752186432","alt":"Adobe Express - Screen Recording 2026-03-10 at 2 30 52 PM-2","r2Key":"releases/d27ed829b6228f6cf80b0b66b44ff03a5556f745a1254bcc13e51a30f880eeb5.mp4","r2Url":"https://media.releases.sh/releases/d27ed829b6228f6cf80b0b66b44ff03a5556f745a1254bcc13e51a30f880eeb5.mp4"}],"coverageCount":0},{"id":"rel_8pwgzIdEgHroTSx5EUt4Y","version":"7.5.0","type":"feature","title":"7.5.0","summary":"Today, we are excited to share the 7.5.0 stable release 🎉 🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X! Highlights ORM Features Added support for nested transaction rollbacks via savepoints (#21678) Adds support for nested…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"Today, we are excited to share the `7.5.0` stable release 🎉\r\n\r\n**🌟 Star this repo for notifications about new releases, bug fixes & features — or [follow us on X](https://pris.ly/x)!**\r\n\r\n\r\n# Highlights\r\n\r\n## ORM\r\n\r\n### Features\r\n\r\n- **Added support for nested transaction rollbacks via savepoints (**[#21678](https://github.com/prisma/prisma/pull/21678))\r\n    \r\n    Adds support for **nested transaction rollback behavior** for SQL databases: if an outer transaction fails, the inner nested transaction is rolled back as well. Implements this by tracking **transaction ID + nesting depth** so Prisma can reuse an existing open transaction in the underlying engine, and it also enables using **`$transaction` from an interactive transaction client**.\r\n    \r\n\r\n### Bug fixes\r\n\r\n**Driver Adapters**\r\n\r\n- Made the  `adapter-mariadb` use the binary MySQL protocol to fix an issue with lossy number conversions ([#29285](https://github.com/prisma/prisma/pull/29285))\r\n- Made `@types/pg` a direct dependency of `adapter-pg` for better TypeScript experience out-of-the-box ([#29277](https://github.com/prisma/prisma/pull/29277))\r\n\r\n**Prisma Client**\r\n\r\n- Resolved `Prisma.DbNull` serializing as empty object in some bundled environments like Next.js ([#29286](https://github.com/prisma/prisma/pull/29286))\r\n- Fixed DateTime fields returning `Invalid Date` with `unixepoch-ms` timestamps in some cases ([#29274](https://github.com/prisma/prisma/pull/29274))\r\n- Fixed a cursor-based pagination issue with `@db.Date` columns ([#29327](https://github.com/prisma/prisma/pull/29327))\r\n\r\n**Schema Engine**\r\n\r\n- Manual partial indexes are now preserved when `partialIndexes` preview feature is disabled, preventing unnecessary drops and additions in migrations ([#5790](https://github.com/prisma/prisma-engines/pull/5790), [#5795](https://github.com/prisma/prisma-engines/pull/5795))\r\n- Enhanced partial index predicate comparison to handle quoted vs unquoted identifiers correctly, eliminating needless recreate cycles ([#5788](https://github.com/prisma/prisma-engines/pull/5788))\r\n- Excluded partial unique indexes from DMMF `uniqueFields` and `uniqueIndexes` to prevent incorrect `findUnique` input type generation ([#5792](https://github.com/prisma/prisma-engines/pull/5792))\r\n\r\n\r\n\r\n## Studio\r\n\r\nWith the launch of Prisma ORM v7, we also introduced a rebuilt version of Prisma Studio. With the feedback we’ve gathered since the release, we’ve added some high requested features to help make Studio a better experience.\r\n\r\n**Multi-cell Selection & Full Table Search**\r\n\r\nThis release brings the ability to select multiple cells when viewing your database. In addition to being able to select multiple cells, you can also search across your database. You can search for a specific table or for specific cells within that table. \r\n\r\n![Adobe Express - CleanShot 2026-03-04 at 21 15 08-2](https://github.com/user-attachments/assets/e3d2aa3d-ae03-47f0-a5d6-3530675864f7)\r\n\r\n\r\n**More intuitive filtering**\r\n\r\nFiltering is now easier to use, and includes an option for raw SQL filters.\r\n\r\n![CleanShot 2026-03-11 at 11 26 35](https://github.com/user-attachments/assets/ba20f670-3770-4dcf-869f-673519bd847c)\r\n\r\n\r\nAnd if you are using Studio in Console, you can use ai generated filters:\r\n![CleanShot 2026-03-11 at 11 28 18](https://github.com/user-attachments/assets/4bd1c328-2429-4fb1-948d-d8d841900f22)\r\n\r\n\r\n\r\n**Cmd+k Command Palette**\r\n\r\nYou can now use the keyboard to perform most actions in Studio with the new cmd+k command palette\r\n![CleanShot 2026-03-11 at 11 30 35](https://github.com/user-attachments/assets/691b7a6e-c677-480c-addc-db42fc2aa9a5)\r\n\r\n\r\n\r\n**Run raw SQL queries**\r\n\r\nAnother feature we’ve included in Prisma Studio is the ability to run raw SQL queries against your data. There’s a new “SQL” tab in the sidebar that will bring you to page where you can perform any queries against your data. Below, we’re getting all the rows in the “Todo” table. \r\n\r\n![Adobe Express - Screen Recording 2026-03-10 at 2 30 52 PM-2](https://github.com/user-attachments/assets/9f3cf91f-23d3-49f1-9cd7-661752186432)\r\n\r\n\r\n## Open roles at Prisma\r\n\r\nInterested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [[Careers page](https://www.prisma.io/careers#current)](https://www.prisma.io/careers#current) and find the role that’s right for you. \r\n\r\n## Enterprise support\r\n\r\nThousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance.\r\n\r\nWith this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise.","publishedAt":"2026-03-11T14:57:08.000Z","fetchedAt":"2026-03-26T19:15:13.501Z","url":"https://github.com/prisma/prisma/releases/tag/7.5.0","media":[],"coverageCount":0},{"id":"rel_qeKYo9bFeH5QfF81lRWvf","version":"7.4.2","type":"feature","title":"7.4.2","summary":"Today, we are issuing a 7.4.2 patch release focused on bug fixes and quality improvements. 🛠 Fixes Prisma Client Fix a case-insensitive IN and NOT IN filter regression (https://github.com/prisma/prisma/pull/29243) Fix a query plan mutation issue that resulted in broken cursor…","titleGenerated":null,"titleShort":null,"breaking":"unknown","importance":null,"content":"Today, we are issuing a 7.4.2 patch release focused on bug fixes and quality improvements.\r\n\r\n## 🛠 Fixes\r\n\r\n**Prisma Client**\r\n- Fix a case-insensitive `IN` and `NOT IN` filter regression (https://github.com/prisma/prisma/pull/29243)\r\n- Fix a query plan mutation issue that resulted in broken cursor queries (https://github.com/prisma/prisma/pull/29262)\r\n- Fix an array parameter wrapping issue in push operations (https://github.com/prisma/prisma-engines/pull/5784)\r\n- Fix `Uint8Array` serialization in nested JSON fields (https://github.com/prisma/prisma/pull/29268)\r\n- Fix an issue with MySQL joins that relied on non-strict equality (https://github.com/prisma/prisma/pull/29251)\r\n\r\n**Driver Adapters**\r\n- **@prisma/adapter-mariadb**: Update text column detection to check for a binary collation (https://github.com/prisma/prisma/pull/29238)\r\n- **@prisma/adapter-mariadb**: Correct `relationJoins` compatibility check for MariaDB 8.x versions (https://github.com/prisma/prisma/pull/29246)\r\n\r\n**Schema Engine**\r\n- Fix partial index predicate comparison on PostgreSQL and MSSQL (https://github.com/prisma/prisma-engines/pull/5780)\r\n\r\n## 🙏 Huge thanks to our community\r\n\r\nMany of the fixes in this release were contributed by our amazing community members. We're grateful for your continued support and contributions that help make Prisma better for everyone!","publishedAt":"2026-02-27T16:38:01.000Z","fetchedAt":"2026-08-26T10:01:54.972Z","url":"https://github.com/prisma/orm/releases/tag/7.4.2","media":[],"coverageCount":0}],"pagination":{"nextCursor":"2026-02-27T16:38:01.000Z|2026-08-26T10:01:54.972Z|rel_qeKYo9bFeH5QfF81lRWvf","limit":20},"summaries":{"rolling":{"windowDays":90,"summary":"Prisma 7 pushed hard on performance and runtime efficiency over this period. The team introduced query result caching in 7.4.0 to eliminate repeated compilation overhead on the event loop, then complemented it with tunable compiler builds in 7.3.0 that let developers trade speed for bundle size. On the adapter front, 7.6.0 expanded driver-specific ergonomics—the pg adapter gained connection string support and custom prepared statement naming, while mariadb toggled between text and binary protocols to fix number precision. Nested transaction rollbacks via savepoints arrived in 7.5.0, enabling proper cleanup when outer transactions fail.","releaseCount":8,"generatedAt":"2026-04-03T19:24:15.164Z"},"monthly":[{"year":2026,"month":2,"summary":"February brought refinement to query handling and adapter support. Prisma shipped 7.4.0 with a new caching layer for the WebAssembly query compiler to reduce event loop contention under high concurrency, addressing the trade-off introduced when the compiler moved onto the JavaScript main thread in version 7. Two patch releases followed, fixing cursor pagination regressions, query plan mutations affecting cursor queries, case-insensitive filter behavior, and compatibility issues in MariaDB and PostgreSQL adapters.","releaseCount":3,"generatedAt":"2026-03-31T14:08:02.414Z"}]}}