@prisma/adapter-planetscale
7.10.1 · 15 Oct 2026Apache-2.069.3k / weekRepositorynpmAtom feed
Upgrading @prisma/adapter-planetscale From 6.17.0 to 7.10.1
22 releases in betweenevery note read
Reading releases, release notes and advisories…
- 20
- changes to make
- 0
- advisories fixed
- 65
- new
- 84
- fixes
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
- 7.10.1
It also updates dependencies that had security advisories.
- 7.10.1
@prisma/adapter-mariadbnow depends onmariadb3.5.4, which fixes several security advisories in 3.5.3. - 7.10.1
- 7.10.0
Binds explicitly to
127.0.0.1instead of all network interfaces. - 7.10.0
Rejects browser requests from origins other than the active
localhostor127.0.0.1Studio URL. - 7.10.0
No longer returns wildcard CORS headers.
- 7.10.0
Applies the same protections across Node.js, Bun, and Deno.
- 7.9.1
Today, we're issuing a patch release to resolve a security advisory in a transitive dependency of Prisma CLI (via
@prisma/dev). - 7.9.0
Resolved the
honosecurity advisories at their source:@prisma/devwas updated to a version that no longer depends onhonoat all, so the CLI is no longer exposed to those advisories through that path. We also patched moderate-severity advisories inajvanduuidacross production dependencies (#29514). - 7.9.0
Hardened the Prisma Platform credentials file (
~/.config/prisma-platform/auth.json) and its directory to0o600/0o700so OAuth tokens are no longer world-readable, bringing Prisma in line with the GitHub, AWS, and Google Cloud CLIs (#29568, from Jaeyoung Yun).
Release by release
- security
It also updates dependencies that had security advisories.
- security
@prisma/adapter-mariadbnow depends onmariadb3.5.4, which fixes several security advisories in 3.5.3. - security
- 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.
- security
- security
Binds explicitly to
127.0.0.1instead of all network interfaces. - security
Rejects browser requests from origins other than the active
localhostor127.0.0.1Studio URL. - security
No longer returns wildcard CORS headers.
- security
Applies the same protections across Node.js, Bun, and Deno.
- security
- security
Today, we're issuing a patch release to resolve a security advisory in a transitive dependency of Prisma CLI (via
@prisma/dev).
- security
- security
Resolved the
honosecurity advisories at their source:@prisma/devwas updated to a version that no longer depends onhonoat all, so the CLI is no longer exposed to those advisories through that path. We also patched moderate-severity advisories inajvanduuidacross production dependencies (#29514). - security
Hardened the Prisma Platform credentials file (
~/.config/prisma-platform/auth.json) and its directory to0o600/0o700so 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
opensslcrate 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/AGENTconventions so future agents are caught without a code change.
- security
- new
Added a
queryPlanCacheMaxSizeoption to thePrismaClientconstructor for fine-grained control over the query plan cache. Pass0to 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
::jsonbcast when filtering on PostgreSQL JSON list columns. Queries usingwhere: { 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), allowingwhere: { 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.
- 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, anddotenv. - new
Migrate — Runs
prisma migrate devif the schema contains models. - new
Generate — Runs
prisma generate. - new
Seed — Runs
prisma db seedif a seed script is configured.
- new
- new
Added a
prisma postgres linkcommand that connects a local project to a Prisma Postgres database. This is the first command in a newprisma postgrescommand group for managing Prisma Postgres databases directly from the CLI. - new
@prisma/adapter-pg: Added a
statementNameGeneratoroption that accepts a custom prepared statement name generator to allow users to leveragepgstatement 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
useTextProtocoloption in the constructor to toggle between text and binary protocols
- new
- new
Added support for nested transaction rollbacks via savepoints (#21678)
- fixed
Made the
adapter-mariadbuse the binary MySQL protocol to fix an issue with lossy number conversions - fixed
Made
@types/pga direct dependency ofadapter-pgfor better TypeScript experience out-of-the-box - fixed
Resolved
Prisma.DbNullserializing as empty object in some bundled environments like Next.js
- new
52 other lines we could not sort, mostly version bumps
- 7.10.0
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
Datevalues passed to$queryRawor$executeRawnow throwPrismaClientValidationErrorinstead of a generic error. #29718 - 7.10.0
Deserialized
Bytesvalues now own standaloneArrayBuffers rather than exposing unrelated contents from Node.js's sharedBufferpool. This applies to both regular and raw query results. #29701 - 7.10.0
Result-extension
computecallbacks now receive the current model name as a typed second argument: - 7.10.0
$on('query')callbacks run within the matchingdb_queryspan. - 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.
4 internal lines (docs, tests, tooling) left out.