@prisma/adapter-d1

7.10.1 · 15 Oct 2026Apache-2.073.1k / weekRepository npm Atom feed

Upgrading @prisma/adapter-d1 From 6.5.0 to 6.6.0

Same major only

1 release in betweenevery note read

Other targets from 6.5.0Newest 6.x6.19.3 Latest7.10.1

6.5.0yours
6.6.0target

5
changes to make: 0
advisories fixed: 11
new: 0
fixes

Start here

Prisma ORM 6.6.0: ESM Support, D1 Migrations & MCP Server

Before you upgrade

Tick each one off as you go

Note: The prisma-client generator is currently in Early Access and will likely have some breaking changes in the next releases.
breaking6.6.0
If you are using the prismaSchemaFolder Preview feature to split your Prisma schema into multiple files, you may encounter some breaking changes in this version.
breaking6.6.0
Pass the the --schema option to your Prisma CLI command (e.g. prisma migrate dev --schema ./prisma/schema)
breaking6.6.0
Set the prisma.schema field in package.json:
breaking6.6.0
Set the schema property in prisma.config.ts:
breaking6.6.0

Release by release

6.6.0
Migration needed8 Apr 202511 new
- breaking
  Note: The prisma-client generator is currently in Early Access and will likely have some breaking changes in the next releases.
- breaking
  If you are using the prismaSchemaFolder Preview feature to split your Prisma schema into multiple files, you may encounter some breaking changes in this version.
- breaking
  Pass the the --schema option to your Prisma CLI command (e.g. prisma migrate dev --schema ./prisma/schema)
- breaking
  Set the prisma.schema field in package.json:

Upgrade to 6.6.0

npm install @prisma/adapter-d1@6.6.0

What 6.6.0 needs

Reading 6.6.0's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 6.6.0. Read once, not stored.

After upgrading

Run the type checker, the linter and the tests.
Build, and look for new deprecation warnings.
Update peer dependencies the new version asks for.