Packages

@prisma/adapter-d1

7.10.1 · 15 Oct 2026Apache-2.073.1k / weekRepositorynpmAtom feed

Upgrading @prisma/adapter-d1 From 5.9.0 to 7.10.1

73 releases in betweenevery note read

Other targets from 5.9.0Newest 5.x5.22.0
  1. 5.9.0yours
  2. 21 releases
  3. 5.22.0security
  4. 6.0.0major
  5. 33 releases
  6. 6.19.3security
  7. 7.0.0major
  8. 7.0.1security
  9. 10 releases
  10. 7.9.0security
  11. 7.9.1security
  12. 7.10.0security
  13. 7.10.1target
  14. 8 pre

Start here

Before you upgrade

Tick each one off as you go
  • breaking7.3.0
  • breaking7.0.0
  • breaking7.0.0
  • breaking7.0.0
  • breaking7.0.0
  • breaking7.0.0
  • breaking7.0.0
  • breaking7.0.0
  • breaking7.0.0
  • breaking7.0.0

Security

  • It also updates dependencies that had security advisories.

    7.10.1
  • @prisma/adapter-mariadb now depends on mariadb 3.5.4, which fixes several security advisories in 3.5.3.

    7.10.1
  • Dependencies with security advisories were updated: mysql2, fast-uri, deepmerge-ts, mariadb and source-map-js. (#30314, #30189, #30668)

    7.10.1
  • Binds explicitly to 127.0.0.1 instead of all network interfaces.

    7.10.0
  • Rejects browser requests from origins other than the active localhost or 127.0.0.1 Studio URL.

    7.10.0
  • No longer returns wildcard CORS headers.

    7.10.0
  • Applies the same protections across Node.js, Bun, and Deno.

    7.10.0
  • Today, we're issuing a patch release to resolve a security advisory in a transitive dependency of Prisma CLI (via @prisma/dev).

    7.9.1
  • 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).

    7.9.0
  • 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, from Jaeyoung Yun).

    7.9.0

Release by release

  1. 7.10.1

    Security fix15 Oct 20262 fixes
    • security

      It also updates dependencies that had security advisories.

    • security

      @prisma/adapter-mariadb now depends on mariadb 3.5.4, which fixes several security advisories in 3.5.3.

    • security

      Dependencies with security advisories were updated: mysql2, fast-uri, deepmerge-ts, mariadb and source-map-js. (#30314, #30189, #30668)

    • fixed

      If the old transaction had committed, the new one failed with P2028;

    • fixed

      If the old transaction was still open, the new one silently ran as a savepoint inside another request's transaction.

  2. 7.10.0

    Security fix25 Aug 20267 new · 8 fixes
    • security

      Binds explicitly to 127.0.0.1 instead of all network interfaces.

    • security

      Rejects browser requests from origins other than the active localhost or 127.0.0.1 Studio URL.

    • security

      No longer returns wildcard CORS headers.

    • security

      Applies the same protections across Node.js, Bun, and Deno.

  3. 7.9.1

    Security fix27 Jul 2026
    • security

      Today, we're issuing a patch release to resolve a security advisory in a transitive dependency of Prisma CLI (via @prisma/dev).

  4. 7.9.0

    Security fix20 Jul 202610 new · 17 fixes
    • security

      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).

    • security

      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, from Jaeyoung Yun).

    • security

      Bumped the openssl crate in the schema engine binaries from 0.10.74 to 0.10.81 (prisma/prisma-engines#5815).

    • new

      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.

  5. 7.8.0

    22 Apr 20261 new · 9 fixes
    • new

      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.

    • fixed

      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)

    • fixed

      Fixed case-insensitive JSON field filtering (mode: insensitive), allowing where: { jsonField: { equals: "...", mode: "insensitive" } } to work correctly. (prisma/prisma-engines#5806)

    • fixed

      Fixed incorrect parameterization of enum values that have a custom database name set via @map.

  6. 7.7.0

    7 Apr 20266 new
    • new

      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. In an existing project without a schema, runs prisma init.

    • new

      Link — Authenticates via the browser and connects to a Prisma Postgres database. Skips if already linked.

    • new

      Install dependencies — Detects the package manager and offers to install missing @prisma/client, prisma, and dotenv.

    • new

      Migrate — Runs prisma migrate dev if the schema contains models.

    • new

      Generate — Runs prisma generate.

    • new

      Seed — Runs prisma db seed if a seed script is configured.

  7. 7.6.0

    27 Mar 20265 new · 6 fixes
    • new

      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.

    • new

      @prisma/adapter-pg: Added a statementNameGenerator option that accepts a custom prepared statement name generator to allow users to leverage pg statement caching

    • new

      @prisma/adapter-pg: Added support for usage of connection strings directly in the constructor for improved ergonomics

    • new

      @prisma/adapter-mariadb: Added a useTextProtocol option in the constructor to toggle between text and binary protocols

  8. 7.5.0

    11 Mar 20261 new · 8 fixes
    • new

      Added support for nested transaction rollbacks via savepoints (#21678)

    • fixed

      Made the adapter-mariadb use the binary MySQL protocol to fix an issue with lossy number conversions

    • fixed

      Made @types/pg a direct dependency of adapter-pg for better TypeScript experience out-of-the-box

    • fixed

      Resolved Prisma.DbNull serializing as empty object in some bundled environments like Next.js

89 other lines we could not sort, mostly version bumps
  • Parameter-chunked statements are now executed atomically in a transaction and rolled back if a later chunk fails. #29771

    7.10.0
  • Improved interactive transaction cleanup during $disconnect(), including transactions whose driver-level startup is still in progress. #28768

    7.10.0
  • Prevented transaction cleanup failures after a timeout or backend termination from becoming unhandled promise rejections. #29611

    7.10.0
  • Invalid Date values passed to $queryRaw or $executeRaw now throw PrismaClientValidationError instead of a generic error. #29718

    7.10.0
  • Deserialized Bytes values now own standalone ArrayBuffers rather than exposing unrelated contents from Node.js's shared Buffer pool. This applies to both regular and raw query results. #29701

    7.10.0
  • Result-extension compute callbacks now receive the current model name as a typed second argument:

    7.10.0
  • $on('query') callbacks run within the matching db_query span.

    7.10.0
  • Events from one operation share the same trace.

    7.10.0
  • Error events are recorded as span exceptions.

    7.10.0
  • Log events continue to be emitted when tracing is disabled or their reported span is unavailable.

    7.10.0

26 internal lines (docs, tests, tooling) left out.