Bump the prisma group with 3 updates

[dependabot]

Bumps the prisma group with 3 updates: @prisma/client, @prisma/generator-helper and prisma.

Updates @prisma/client from 6.11.1 to 6.12.0

Release notes

Sourced from @​prisma/client's releases.

6.12.0

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

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

Highlights

ESM-compatible prisma-client generator now in Preview

We’re excited to share that our new and more flexible prisma-client generator is moving into Preview! As a reminder, here’s what it looks like:

generator client {
  // Required
  provider = "prisma-client" // no `-js` at the end!
  output   = "../src/generated/prisma"
// Optional
runtime                = "nodejs"
moduleFormat           = "esm"
generatedFileExtension = "ts"
importFileExtension    = "ts"
}

This new generator eliminates any headaches that you may have experienced due to magical code generation into node_modules and gives you full control over the generated Prisma Client code. With it moving into Preview, we hope that even more of you will try it out and share your feedback with us!

Note: The prisma-client generator will become the default in Prisma v7, replacing the current prisma-client-js generator.

In addition to moving it into Preview, we also created a couple of new ready-to-run examples to help you get started with the new generator and your favorite framework:

• React Router + Vite + Cloudflare
• React Router + Vite + Node.js
• Nuxt 3 + Vite + Nitro
• Deno Deploy

📚 Learn more in the docs.

Specify views and migrations folder locations in prisma.config.ts (Early Access)

As we’re getting closer to the General Availability release of prisma.config.ts, we’re adding more capabilities to it. In previous versions, the Prisma CLI implicitly used to infer the location for migration and SQL view definition files based on the location of the Prisma schema. In this release, we’re adding two new fields (migrations and views) to give you more flexibility and clarity on how to locate these files:

// prisma.config.ts
export default defineConfig({
  earlyAccess: true,
  migrations: {
    path: './db/migrations'
  },
  views: {
</tr></table> 

... (truncated)

Commits

• 533dd62 chore(deps): update engines to 6.12.0-15.8047c96bbd92db98a2abc7c9323ce77c02c8...
• 4b423f3 fix(client): never ignore the configured adapter in ClientEngine (#27644)
• 150f58c chore(deps): update engines to 6.12.0-14.cf92c4bfad34aa635b071a7d483b78c3975b...
• 02e63fd feat(client): support Accelerate in ClientEngine (#27594)
• c693620 chore(client): include runtime sourcemaps in the published package (#27567)
• 506bb22 fix(client): fixed queryCompiler on esbuild + cjs (#27610)
• b0ce6dc chore(deps): update engines to 6.12.0-13.c4261e444b23ae1c84edf7bd1b551230d4c6...
• e9dc21a chore(deps): update engines to 6.12.0-10.7bac10d77abc289ba496f5e0fb810302ddfa...
• 2ffd987 chore(deps): update engines to 6.12.0-8.1a6322a0d75e102dfa53553afc7987d0de76f...
• 9ae6cf8 chore(deps): update engines to 6.12.0-7.c238eea7bd55fe78a5fbd21d9119bee49f0ee...
• Additional commits viewable in compare view

Updates @prisma/generator-helper from 6.11.1 to 6.12.0

Release notes

Sourced from @​prisma/generator-helper's releases.

6.12.0

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

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

Highlights

ESM-compatible prisma-client generator now in Preview

We’re excited to share that our new and more flexible prisma-client generator is moving into Preview! As a reminder, here’s what it looks like:

generator client {
  // Required
  provider = "prisma-client" // no `-js` at the end!
  output   = "../src/generated/prisma"
// Optional
runtime                = "nodejs"
moduleFormat           = "esm"
generatedFileExtension = "ts"
importFileExtension    = "ts"
}

This new generator eliminates any headaches that you may have experienced due to magical code generation into node_modules and gives you full control over the generated Prisma Client code. With it moving into Preview, we hope that even more of you will try it out and share your feedback with us!

Note: The prisma-client generator will become the default in Prisma v7, replacing the current prisma-client-js generator.

In addition to moving it into Preview, we also created a couple of new ready-to-run examples to help you get started with the new generator and your favorite framework:

• React Router + Vite + Cloudflare
• React Router + Vite + Node.js
• Nuxt 3 + Vite + Nitro
• Deno Deploy

📚 Learn more in the docs.

Specify views and migrations folder locations in prisma.config.ts (Early Access)

As we’re getting closer to the General Availability release of prisma.config.ts, we’re adding more capabilities to it. In previous versions, the Prisma CLI implicitly used to infer the location for migration and SQL view definition files based on the location of the Prisma schema. In this release, we’re adding two new fields (migrations and views) to give you more flexibility and clarity on how to locate these files:

// prisma.config.ts
export default defineConfig({
  earlyAccess: true,
  migrations: {
    path: './db/migrations'
  },
  views: {
</tr></table> 

... (truncated)

Commits

• cbb9810 chore(deps-dev): bump esbuild from 0.25.1 to 0.25.5 (#27581)
• See full diff in compare view

Updates prisma from 6.11.1 to 6.12.0

Release notes

Sourced from prisma's releases.

6.12.0

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

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

Highlights

ESM-compatible prisma-client generator now in Preview

We’re excited to share that our new and more flexible prisma-client generator is moving into Preview! As a reminder, here’s what it looks like:

generator client {
  // Required
  provider = "prisma-client" // no `-js` at the end!
  output   = "../src/generated/prisma"
// Optional
runtime                = "nodejs"
moduleFormat           = "esm"
generatedFileExtension = "ts"
importFileExtension    = "ts"
}

This new generator eliminates any headaches that you may have experienced due to magical code generation into node_modules and gives you full control over the generated Prisma Client code. With it moving into Preview, we hope that even more of you will try it out and share your feedback with us!

Note: The prisma-client generator will become the default in Prisma v7, replacing the current prisma-client-js generator.

In addition to moving it into Preview, we also created a couple of new ready-to-run examples to help you get started with the new generator and your favorite framework:

• React Router + Vite + Cloudflare
• React Router + Vite + Node.js
• Nuxt 3 + Vite + Nitro
• Deno Deploy

📚 Learn more in the docs.

Specify views and migrations folder locations in prisma.config.ts (Early Access)

As we’re getting closer to the General Availability release of prisma.config.ts, we’re adding more capabilities to it. In previous versions, the Prisma CLI implicitly used to infer the location for migration and SQL view definition files based on the location of the Prisma schema. In this release, we’re adding two new fields (migrations and views) to give you more flexibility and clarity on how to locate these files:

// prisma.config.ts
export default defineConfig({
  earlyAccess: true,
  migrations: {
    path: './db/migrations'
  },
  views: {
</tr></table> 

... (truncated)

Commits

• 9e35c80 fix(cli): always return valid JSON from MCP server (#27576)
• 0345aa9 fix: copy wasm files to output path in prisma-client generator (#27623)
• 4b4215f feat(config): add support for custom path for migrations, views, `typed...
• 0eab160 feat(config): lift "config.migrate.adapter" into "config.adapter" (#27618)
• cbb9810 chore(deps-dev): bump esbuild from 0.25.1 to 0.25.5 (#27581)
• See full diff 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 <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

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
comiacapay	❌ Failed (Inspect)			Aug 4, 2025 10:06am

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.