[Snyk] Upgrade prisma from 6.11.1 to 6.12.0

[iamspathan]

Snyk has created this PR to upgrade prisma from 6.11.1 to 6.12.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 50 versions ahead of your current version.

• The recommended version was released a month ago.

Release notes

Package name: prisma

• 6.12.0 - 2025-07-15
  

  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: {
      path: './db/views'
    }
    // ...
  })

  📚 Learn more in the docs.

  Enterprise support

  Thousands of teams use Prisma and many of them already tap into our Enterprise & Agency Support Program for hands-on help with everything from schema integrations and performance tuning to security and compliance. With this program you also get priority issue triage and bug fixes, expert scalability advice, and custom training so that your Prisma-powered apps stay rock-solid at any scale. Learn more or join: https://prisma.io/enterprise

• 6.12.0-integration-raw-code-fallback-turso.1 - 2025-07-14
• 6.12.0-integration-push-nqqtxovowlmm.3 - 2025-07-14
• 6.12.0-integration-push-nqqtxovowlmm.2 - 2025-07-11
• 6.12.0-integration-push-nqqtxovowlmm.1 - 2025-07-10
• 6.12.0-integration-fix-support-adapter-type-in-prisma-client-constructor-with-edge-runtimes.1 - 2025-07-11
• 6.12.0-integration-fix-regression-accelerate.1 - 2025-07-02
• 6.12.0-integration-fix-mcp-json-response.3 - 2025-07-03
• 6.12.0-integration-fix-mcp-json-response.2 - 2025-07-03
• 6.12.0-integration-fix-mcp-json-response.1 - 2025-07-02
• 6.12.0-integration-feat-investigate-prisma-generate-on-stackblitz.1 - 2025-07-14
• 6.12.0-dev.40 - 2025-07-15
• 6.12.0-dev.39 - 2025-07-15
• 6.12.0-dev.38 - 2025-07-15
• 6.12.0-dev.37 - 2025-07-15
• 6.12.0-dev.36 - 2025-07-15
• 6.12.0-dev.35 - 2025-07-14
• 6.12.0-dev.34 - 2025-07-14
• 6.12.0-dev.33 - 2025-07-14
• 6.12.0-dev.32 - 2025-07-14
• 6.12.0-dev.31 - 2025-07-11
• 6.12.0-dev.30 - 2025-07-10
• 6.12.0-dev.29 - 2025-07-10
• 6.12.0-dev.28 - 2025-07-10
• 6.12.0-dev.27 - 2025-07-10
• 6.12.0-dev.26 - 2025-07-10
• 6.12.0-dev.25 - 2025-07-10
• 6.12.0-dev.24 - 2025-07-10
• 6.12.0-dev.23 - 2025-07-10
• 6.12.0-dev.22 - 2025-07-09
• 6.12.0-dev.21 - 2025-07-09
• 6.12.0-dev.20 - 2025-07-09
• 6.12.0-dev.19 - 2025-07-09
• 6.12.0-dev.18 - 2025-07-04
• 6.12.0-dev.17 - 2025-07-04
• 6.12.0-dev.16 - 2025-07-03
• 6.12.0-dev.15 - 2025-07-03
• 6.12.0-dev.14 - 2025-07-03
• 6.12.0-dev.13 - 2025-07-03
• 6.12.0-dev.12 - 2025-07-03
• 6.12.0-dev.11 - 2025-07-02
• 6.12.0-dev.10 - 2025-07-02
• 6.12.0-dev.9 - 2025-07-02
• 6.12.0-dev.8 - 2025-07-01
• 6.12.0-dev.7 - 2025-07-01
• 6.12.0-dev.6 - 2025-07-01
• 6.12.0-dev.4 - 2025-07-01
• 6.12.0-dev.3 - 2025-07-01
• 6.12.0-dev.2 - 2025-07-01
• 6.12.0-dev.1 - 2025-07-01
• 6.11.1 - 2025-07-03
  

  Today, we are issuing a 6.11.1 patch release.

  Bug fixes

  • In Prisma ORM version 6.11.0, we shipped a bug fix for Prisma that allows using Prisma Postgres with direct TCP connections with Prisma Driver Adapters. This fix required refactoring the Prisma Client initialization logic, and while several test cases were added, an edge case was missing, causing #27569.
    Namely, using @ prisma/client with @ prisma/extension-accelerate on a prisma+postgres://... connection string, while generating the Prisma Client definitions via prisma generate, resulted in a PrismaClientInitializationError.

    This is now fixed, so we highly recommend upgrading to version 6.11.1.

    Reminder: when using Prisma Accelerate, we highly encourage you to generate your Prisma Client definitions via prisma generate --no-engine.

  • We've fixed an issue that would occur when using arrays as aggregation fields with the query compiler. These queries would fail with a confusing data mapping error. They should now work as expected.

from prisma GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs