Skip to content

Bump the prisma group with 2 updates - #404

Merged
dependabot[bot] merged 1 commit into
masterfrom
dependabot/npm_and_yarn/prisma-1be2217b75
Sep 11, 2025
Merged

Bump the prisma group with 2 updates#404
dependabot[bot] merged 1 commit into
masterfrom
dependabot/npm_and_yarn/prisma-1be2217b75

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 11, 2025

Copy link
Copy Markdown
Contributor

Updates the requirements on @prisma/client and prisma to permit the latest version.
Updates @prisma/client to 6.16.0

Release notes

Sourced from @​prisma/client's releases.

6.16.0

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

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

Prisma ORM

This section contains all the updates made in Prisma ORM v6.16.0.

Rust-free ORM and driver adapters are Generally Available

Eight months ago, we published our ORM manifesto with the first hint that we're going to remove the Rust-based query engine from Prisma ORM:

We're addressing this by migrating Prisma's core logic from Rust to TypeScript and redesigning the ORM to make customization and extension easier.

After a lot of hard work and feedback from the community, we're incredibly excited to share that the migration has been completed and you can now use Prisma ORM without its Rust engine in your production apps. 🎉 This is a major milestone in the history of Prisma ORM and comes with a lot of benefits:

  • Reduced bundle size by ~90%
  • Faster queries (check out our latest benchmarks)
  • Lower CPU footprint
  • Less deployment complexity
  • Easier to make open-source contributions

… and overall a much better DX since you don't need to worry about the extra binary in your generated Prisma Client code any more.

While the Rust-free ORM will become the default in Prisma ORM v7 soon, for now you still need to opt-into using it:

  1. Configure the generator block in your Prisma schema:
    generator client {
      provider   = "prisma-client" // (or "prisma-client-js") 
      output     = "../src/generated/prisma"
      engineType = "client"
    }
    Note: If you tried the Rust-free ORM before, you can now also drop the queryCompiler and driverAdapter feature flags from the previewFeatures array. And if you used binaryTargets, you can also get rid of these.
  2. Install the driver adapter for your database, e.g. to use pg for PostgreSQL:
    npm install @prisma/adapter-pg
    
  3. Finally, you can instantiate PrismaClient using the PrismaPg driver adapter as follows:
    import { PrismaClient } from './generated/prisma'
    import { PrismaPg } from '@prisma/adapter-pg'
    const adapter = new PrismaPg({ connectionString: env.DATABASE_URL })
    const prisma = new PrismaClient({ adapter })
    // ... send queries using prisma like before

... (truncated)

Commits
  • abfa3a6 feat(client): add /browser entrypoint to prisma-client (#28068)
  • 5715816 fix(qpe): flip condition when choosing whether to enable itx manager (#28069)
  • 898066a feat(client-generator-ts): removed "Prisma.Validator" from "prisma-client" ge...
  • bc18826 fix(client): add apiKey method for Accelerate extension (#28067)
  • 83cd003 feat(client-generator-ts): re-export enums directly in prisma-client genera...
  • 38b3397 feat(client): remove node_modules caching check when generator has custom out...
  • 9d1b883 feat(qc): stabilize driver adapters and the query compiler (#28046)
  • 98895b6 chore(deps): update engines to 6.16.0-7.1c57fdcd7e44b29b9313256c76699e91c3ac3...
  • 493cf1c test(client): run qc tests with remote executor (#27971)
  • 9938768 fix(generator-js): don't break QC with --no-engine (#28042)
  • Additional commits viewable in compare view

Updates prisma to 6.16.0

Release notes

Sourced from prisma's releases.

6.16.0

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

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

Prisma ORM

This section contains all the updates made in Prisma ORM v6.16.0.

Rust-free ORM and driver adapters are Generally Available

Eight months ago, we published our ORM manifesto with the first hint that we're going to remove the Rust-based query engine from Prisma ORM:

We're addressing this by migrating Prisma's core logic from Rust to TypeScript and redesigning the ORM to make customization and extension easier.

After a lot of hard work and feedback from the community, we're incredibly excited to share that the migration has been completed and you can now use Prisma ORM without its Rust engine in your production apps. 🎉 This is a major milestone in the history of Prisma ORM and comes with a lot of benefits:

  • Reduced bundle size by ~90%
  • Faster queries (check out our latest benchmarks)
  • Lower CPU footprint
  • Less deployment complexity
  • Easier to make open-source contributions

… and overall a much better DX since you don't need to worry about the extra binary in your generated Prisma Client code any more.

While the Rust-free ORM will become the default in Prisma ORM v7 soon, for now you still need to opt-into using it:

  1. Configure the generator block in your Prisma schema:
    generator client {
      provider   = "prisma-client" // (or "prisma-client-js") 
      output     = "../src/generated/prisma"
      engineType = "client"
    }
    Note: If you tried the Rust-free ORM before, you can now also drop the queryCompiler and driverAdapter feature flags from the previewFeatures array. And if you used binaryTargets, you can also get rid of these.
  2. Install the driver adapter for your database, e.g. to use pg for PostgreSQL:
    npm install @prisma/adapter-pg
    
  3. Finally, you can instantiate PrismaClient using the PrismaPg driver adapter as follows:
    import { PrismaClient } from './generated/prisma'
    import { PrismaPg } from '@prisma/adapter-pg'
    const adapter = new PrismaPg({ connectionString: env.DATABASE_URL })
    const prisma = new PrismaClient({ adapter })
    // ... send queries using prisma like before

... (truncated)

Commits

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 will merge this PR once CI passes on it, as requested by @samchon.


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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Updates the requirements on [@prisma/client](https://github.com/prisma/prisma/tree/HEAD/packages/client) and [prisma](https://github.com/prisma/prisma/tree/HEAD/packages/cli) to permit the latest version.

Updates `@prisma/client` to 6.16.0
- [Release notes](https://github.com/prisma/prisma/releases)
- [Commits](https://github.com/prisma/prisma/commits/6.16.0/packages/client)

Updates `prisma` to 6.16.0
- [Release notes](https://github.com/prisma/prisma/releases)
- [Commits](https://github.com/prisma/prisma/commits/6.16.0/packages/cli)

---
updated-dependencies:
- dependency-name: "@prisma/client"
  dependency-version: 6.16.0
  dependency-type: direct:production
  dependency-group: prisma
- dependency-name: prisma
  dependency-version: 6.16.0
  dependency-type: direct:production
  dependency-group: prisma
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 11, 2025
@samchon

samchon commented Sep 11, 2025

Copy link
Copy Markdown
Owner

@dependabot merge

@dependabot
dependabot Bot merged commit c13eac4 into master Sep 11, 2025
5 checks passed
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/prisma-1be2217b75 branch September 11, 2025 09:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant