Prisma 6.8.0stable Released May 15, 2025
Impact Score: 5/10

Prisma 6.8.0 — Release Notes & Engineering Impact

Source available — automated, not human-reviewed

Component: prisma · Channel: stable. Automated analysis, not a compatibility certification. How this works.

Analysis updated: 2026-11-01.

Compatibility not verified — check source notes
$ npm install --save-dev --save-exact [email protected]
📄 .MD
⚡ Executive Summary (TL;DR)

Prisma 6.8.0. Source highlight: Today, we are excited to share the `6.8.0` stable release 🎉

Who Does This Impact? (Role-Based Analysis)

💻 Software Engineers & Devs

Check the source notes against the package and APIs you use before upgrading.

📊 Product & Engineering Leads

Use the documented changes to assess relevance to your product; release frequency alone is not a quality measure.

⚙️ DevOps & Security

Verify the target version, runtime requirements and rollback procedure in the official documentation.

📄 View Raw Release Notes (Original Developer Log)
Today, we are excited to share the `6.8.0` stable release 🎉  🌟 **Help us spread the word about Prisma by starring the repo ☝️ or [posting on X](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v6.8.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/6.8.0) about the release.** ## Highlights ### Local development with Prisma Postgres via `prisma dev` (Early Access) In this release, we're releasing a way to develop against Prisma Postgres _locally_ — no Docker required! To get started, run the new `prisma dev` command: ```bash npx prisma dev # starts a local Prisma Postgres server ``` This command spins up a local Prisma Postgres instance and prints the connection URL that you'll need to set as the `url` of your `datasource` block to point to a local Prisma Postgres instance. It looks similar to this: ```prisma datasource db { provider = "postgresql" url = "prisma+postgres://localhost:51213/?api_key=ey..." } ``` You can then run migrations and execute queries against this local Prisma Postgres instance as with any remote one. Note that you need to keep the `prisma dev` process running in order to interact with the local Prisma Postgres instance. 📚 Learn more in the [docs](https://www.prisma.io/docs/postgres/database/local-development). ### Native Deno support in `prisma-client` generator (Preview) In this release, we're removing the `deno` Preview feature from the `prisma-client-js` generator. If you want to use Prisma ORM with Deno, you can now do so with the new [`prisma-client`](https://www.prisma.io/docs/orm/prisma-schema/overview/generators#prisma-client-early-access) generator: ```prisma generator client { provider = "prisma-client" output = "../src/generated/prisma" runtime = "deno" } ``` 📚 Learn more in the [docs](https://www.prisma.io/docs/orm/prisma-client/deployment/edge/deploy-to-deno-deploy). ### VS Code Agent Mode: AI support with your database workflows Have you tried [agent mode in VS Code](https://code.visualstudio.com/blogs/2025/04/07/agentMode) already? _"The agent acts as an **autonomous pair programmer** that performs multi-step coding tasks at your command, such as analyzing your codebase, proposing file edits, and running terminal commands."_ As of this release, your agent is capable of supporting you with your database workflows more than ever! If you're using VS Code and have the Prisma VS Code extension installed, your agent now is able to help you with your database workflows, such as: - checking the status of your migrations (e.g. telling you if migrations haven't been applied) - creating and running schema migrations for you - authenticating you with the Prisma Console - provisioning new Prisma Postgres instances so you can start coding right away All you need to do is make sure you're using the latest version of [Prisma's VS Code extension](https://marketplace.visualstudio.com/items?itemName=Prisma.prisma) and your agent is ready to go 🚀 📚 Learn more in the [docs](https://www.prisma.io/docs/postgres/integrations/vscode-agent). ## Other news ### You voted, we acted: New Singapore region for Prisma Postgres We recently [ran a poll](https://x.com/prisma/status/1916808960868552943) where we asked you which region you'd like to see next for Prisma Postgres. The majority vote went to **Asia Pacific (Singapore)**, so as of today, you're able to spin up new Prisma Postgres instances in the `ap-southeast-1` region. We're not stopping here — [keep an eye out on X](https://pris.ly/x) for another poll asking for your favorite regions that we should add!