Bump @prisma/client from 5.1.1 to 6.10.0

[dependabot]

Bumps @prisma/client from 5.1.1 to 6.10.0.

Release notes

Sourced from @​prisma/client's releases.

6.10.0

Today, we are excited to share the 6.10.0 stable release 🎉 

🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.

Highlights

No Rust engines for MS SQL Server & PlanetScale (Preview)

We are in the process of removing the Rust engines from Prisma ORM. If you want to try this, you can configure your generator like this:

generator client {
  provider        = "prisma-client-js" // or `prisma-client`
  output          = "../generated/prisma"
  previewFeatures = ["queryCompiler", "driverAdapters"]
}

In this release, we are excited to move the queryCompiler (which enables using Prisma ORM without Rust engines) into Preview for MS SQL Server and PlanetScale (via the new @prisma/adapter-mssql and existing @prisma/adapter-planetscale driver adapters).

📚Learn more in the docs.

Manage local Prisma Postgres instances in VS Code

We recently released a database management UI as part of the Prisma VS Code extension to enable visual database management workflows for Prisma Postgres. In this release, we added new functionality to it: You can now manage multiple local Prisma Postgres instances via the same UI. To try it, find the Prisma logo in VS Code’s sidebar and start managing your local Prisma Postgres instances (no Docker required).

📚 Learn more in the docs.

Performance improvements for prisma migrate dev

We improved the prisma migrate dev command by optimizing the interactions with the shadow database. Our measurements show a 2x improvement in speed for some databases!

"Push to Cloud": Easily deploy a local Prisma Postgres instance in VS Code

Local Prisma Postgres instances are perfect for development, but how do you go from local to remote once you’re ready to deploy?

The database management UI in VS Code now has a Push to Cloud button that makes it easy to deploy your local Prisma Postgres so that you can connect to it from your deployed applications.

📚 Learn more in the docs.

Support for shard keys on PlanetScale (Preview)

Sharding is a popular technique to scale up when database load grows. As of this release, Prisma ORM supports sharding on PlanetScale natively via the new @shardKey and @@shardKey attributes in the Prisma schema which you can apply to the fields in your models that should serve as shard keys in your database setup:

// Single-column shard key
model User {
  id     String @default(uuid())
  region String @shardKey
</tr></table> 

... (truncated)

Commits

• 4c2b06f chore(deps): update engines to 6.10.0-43.aee10d5a411e4360c6d3445ce4810ca65adb...
• 17ea178 test(client): fix 27128-generate-watch e2e test (#27434)
• 8dd746b chore(deps): update engines to 6.10.0-42.39043d8aab90e284b564f5c67b8ee5b37fa2...
• f572d8a chore(deps): update engines to 6.10.0-41.ab8c8f5e7182107cd696538d48aa8f76924b...
• d285f48 fix: various mssql fixes (#27426)
• 6de1062 chore(deps): update engines to 6.10.0-40.c46ef19af4e86c0aeea749943e5f784fef70...
• a7d6432 feat: MSSQL driver adapter (#27373)
• b7f1318 chore(deps): update engines to 6.10.0-33.de286ec151f15c603ffe67ce23f9e01a3ef4...
• 3fe3830 feat(generator): ORM-854 drop index.ts from new generator (#27394)
• 3b4fa1d chore(deps): update engines to 6.10.0-27.82e51782269a54204161ed884d4fd805c810...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
web	❌ Failed (Inspect)			Jun 18, 2025 4:55pm

[dependabot]

Superseded by #570.