chore(deps): bump the prisma group with 2 updates

[dependabot]

Bumps the prisma group with 2 updates: @prisma/client and prisma.

Updates @prisma/client from 6.18.0 to 7.0.0

Release notes

Sourced from @​prisma/client's releases.

7.0.0

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

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

Highlights

Over the past year we focused on making it simpler and faster to build applications with Prisma, no matter what tools you use or where you deploy, with exceptional developer experience at it’s core. This release makes many features introduced over the past year as the new defaults moving forward.

Prisma ORM

Rust-free Prisma Client as the default

The Rust-free Prisma Client has been in the works for some time now, all the way back to v6.16.0, with early iterations being available for developers to adopt. Now with version 7.0, we’re making this the default for all new projects. With this, developers are able to get:

• ~90% smaller bundle sizes
• Up to 3x faster queries
• ESM-first Prisma Client
• Significantly simpler deployments

Adopting the new Rust-free client is as simple as swapping the prisma-client-js provider for prisma-client in your main schema.prisma :

// schema.prisma
generator client {
-	provider = "prisma-client-js"
+ provider = "prisma-client"
}

Generated Client and types move out of node_modules

When running prisma generate, the generated Client runtime and project types will now require a output path to be set in your project’s main schema.prisma. We recommend that they be generated inside of your project’s src directory to ensure that your existing tools are able to consume them like any other piece of code you might have.

// schema.prisma
generator client {
  provider = "prisma-client"
  // Generate my Client and Project types 
  output   = "../src/generated/prisma"
}

Update your code to import PrismaClient from this generated output:

// Import from the generated prisma client
import { PrismaClient } from './generated/prisma/client';

... (truncated)

Commits

• bc09f97 feat(client): made accelerateUrl and adapter mutually exclusive at type level...
• 3bf3163 chore: update engines to 6.20.0-16.next-0c19ccc313cf9911a90d99d2ac2eb0280c76c513
• bdb03a5 fix(client): remove and fix remains of QE runtime bundles (#28533)
• 3576780 feat(cli,migrate)!: resolve datasource paths relative to the config (#28514)
• 41837be fix: fix usage of prisma init with corepack (#28504)
• 1fb6761 feat(config): remove support for engine: 'js' | 'classic'; remove experimen...
• d1cb099 refactor: remove legacy cruft from GetPrismaClientOptions (#28496)
• fc75dbc fix: fix 21136 extension test (#28497)
• df11516 feat(client): [breaking] remove postinstall hook, remove "auto-install" on ...
• ff9d7cb chore: bump engines to 6.20.0-11.next-80ee0a44bf5668992b0c909c946a755b86b56c95
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​prisma/client since your current version.

Updates prisma from 6.18.0 to 7.0.0

Release notes

Sourced from prisma's releases.

7.0.0

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

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

Highlights

Over the past year we focused on making it simpler and faster to build applications with Prisma, no matter what tools you use or where you deploy, with exceptional developer experience at it’s core. This release makes many features introduced over the past year as the new defaults moving forward.

Prisma ORM

Rust-free Prisma Client as the default

The Rust-free Prisma Client has been in the works for some time now, all the way back to v6.16.0, with early iterations being available for developers to adopt. Now with version 7.0, we’re making this the default for all new projects. With this, developers are able to get:

• ~90% smaller bundle sizes
• Up to 3x faster queries
• ESM-first Prisma Client
• Significantly simpler deployments

Adopting the new Rust-free client is as simple as swapping the prisma-client-js provider for prisma-client in your main schema.prisma :

// schema.prisma
generator client {
-	provider = "prisma-client-js"
+ provider = "prisma-client"
}

Generated Client and types move out of node_modules

When running prisma generate, the generated Client runtime and project types will now require a output path to be set in your project’s main schema.prisma. We recommend that they be generated inside of your project’s src directory to ensure that your existing tools are able to consume them like any other piece of code you might have.

// schema.prisma
generator client {
  provider = "prisma-client"
  // Generate my Client and Project types 
  output   = "../src/generated/prisma"
}

Update your code to import PrismaClient from this generated output:

// Import from the generated prisma client
import { PrismaClient } from './generated/prisma/client';

... (truncated)

Commits

• 1778827 feat(cli): update prisma init --db output (#28551)
• 9558e9e feat(cli): MySQL + Studio fully functional. 🐬 (#28542)
• 447e03a feat: implement the studio telemetry endpoint (#28560)
• 61dd871 fix: fix sqlite node 20 studio issues (#28552)
• 2f4a80c fix: clarify the message about supported Node.js versions (#28545)
• 12f0e27 feat(cli): improve prisma init output (#28546)
• 944cd0c feat(cli): Studio + MySQL 🐬 (#28537)
• cc6f6e5 feat(cli): change custom generator example in help text (#28539)
• a1136ea feat(cli): re-introduce init as an eager command. (#28538)
• af62fd8 feat(cli): Studio + SQLite baaaaaaaby! (#28511)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for prisma since your current version.

You can trigger a rebase of this PR 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 <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

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​prisma/​client@​6.18.0 ⏵ 7.2.0	+5
	prisma@​6.18.0 ⏵ 7.2.0				+1

View full report

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.