Sourced from prisma's releases.

6.11.1

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, however, required refactoring the of the Prisma Client initialization logic, and while several test cases were added, an edge case was missing, causing prisma/prisma#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.

6.11.0

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

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

Highlights

Prisma ORM without Rust engines for MySQL/MariaDB, Neon & CockroachDB (Preview)

We are in the process of removing the Rust engines from Prisma ORM. This week, we're adding Preview support for the Rust-free Prisma ORM version for MySQL via a new @prisma/adapter-mariadb driver adapter, as well as for Neon and CockroachDB via the already existing @prisma/adapter-neon and @prisma/adapter-pg adapters.

Note: The mariadb driver is compatible with all MySQL databases. It's the recommended option to use MySQL with Prisma ORM when using driver adapters.

To use it, enable the queryCompiler and driverAdapters feature flags on your generator block, install the driver adapter for your database and start querying!

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

📚Learn more in the docs.

Stop and remove local Prisma Postgres instances via CLI

You can start a local Prisma Postgres instance using the prisma dev --name mydb command or via the Prisma VS Code extension UI.

If you start a local instance via the Prisma CLI, you can simply kill the process to stop the instance. However, when you start instances via the VS Code extension UI, you could also only stop them via the UI—not via the CLI.

This changes in this release: You can now also stop local Prisma Postgres instances and remove them from your file system via the Prisma CLI:

• prisma dev stop <globs>: Stops one or more local Prisma Postgres instances

... (truncated)

• 1ea2d4e chore(cli): update mcp sdk dependency (#27551)
• 8efbdc5 docs: add reference to MCP server repo (#27501)
• 86dc695 feat(tracking): ORM-1125 only track known top level commands (#27464)
• 604e937 test(cli): fix version snapshot with custom WASM components (#27444)
• 42166a0 feat: add RunnableContext object as additional arg passed to dynamic subcomma...
• 643b4f3 fix: ORM-1006 fix subcommands like init (#27400)
• 4594b5d feat(CLI): anonymously track all commands, regardless of success/failure. (#2...
• ee58663 feat(cli): avoid lookup of engines in "prisma version" if possible; showcase ...
• aa47fc6 feat(client): skip download in getGenerators when queryCompiler is turned...
• e76c711 feat(cli): skip downloading Query Engine when Query Compiler is turned on, an...
• Additional commits viewable in compare view

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)