deps: update prisma to 7.3.0 #9

2026-02-04T08:21:41-08:00

minori commented

2026-02-04 08:21:41 -08:00

Dependency Update

Updates prisma from 6.4.1 to 7.3.0.

Type

devDependencies

Changelog

7.3.0

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

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

ORM

#28976: Fast and Small Query Compilers
We've been working on various performance-related bugs since the initial ORM 7.0 release. With 7.3.0, we're introducing a new compilerBuild option for the client generator block in schema.prisma with two options: fast and small. This allows you to swap the underlying Query Compiler engine based on your selection, one built for speed (with an increase in size), and one built for size (with the trade off for speed). By default, the fast mode is used, but this can be set by the user:

generator client {
  provider = "prisma-client"
  output   = "../src/generated/prisma"
  compilerBuild = "fast" // "fast" | "small"
}

We still have more in progress for performance, but this new compilerBuild option is our first step toward addressing your concerns!

#29005: Bypass the Query Compiler for Raw Queries
Raw queries ($executeRaw, $queryRaw) can now skip going through the query compiler and query interpreter infrastructure. They can be sent directly to the driver adapter, removing additional overhead.
#28965: Update MSSQL to v12.2.0
This community PR updates the @prisma/adapter-mssql to use MSSQL v12.2.0. Thanks Jay-Lokhande!
#29001: Pin better-sqlite3 version to avoid SQLite bug
An underlying bug in SQLite 3.51.0 has affected the better-sqlite3 adapter. We’ve bumped the version that powers @prisma/better-sqlite3 and have pinned the version to prevent any unexpected issues. If you are using @prisma/better-sqlite3 , please upgrade to v7.3.0.
#29002: Revert @map enums to v6.19.0 behavior
In the initial release of v7.0, we made a change with Mapped Enums where the generated enum would get its value from the value passed to the @map function. This was a breaking change from v6 that caused issues for many users. We have reverted this change for the time being, as many different diverging approaches have emerged from the community discussion.
prisma-engines#5745: Cast BigInt to text in JSON aggregation
When using relationJoins with BigInt fields in Prisma 7, JavaScript's JSON.parse loses precision for integers larger than Number.MAX_SAFE_INTEGER (2^53 - 1). This happens because PostgreSQL's JSONB_BUILD_OBJECT returns BigInt values as JSON numbers, which JavaScript cannot represent precisely.
```
// Original BigInt ID: 312590077454712834
// After JSON.parse: 312590077454712830 (corrupted!)
```
This PR cast BigInt columns to ::text inside JSONB_BUILD_OBJECT calls, similar to how MONEY is already cast to ::numeric.
```
-- Before
JSONB_BUILD_OBJECT('id', "id")

-- After
JSONB_BUILD_OBJECT('id', "id"::text)
```

This ensures BigInt values are returned as JSON strings, preserving full precision when parsed in JavaScript.

Open roles at Prisma

Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [Careers page](https://www.prisma.io/careers#current) and find the role that’s right for you.

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.

7.2.0

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

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

Highlights

ORM

#28830: feat: add sqlcommenter-query-insights plugin
- Adds a new SQL commenter plugin to support query insights metadata.
#28860: feat(migrate): add -url param for db pull, db push, migrate dev
- Adds a -url flag to key migrate commands to make connection configuration more flexible.
#28895: feat(config): allow undefined URLs in e.g. prisma generate
- Allows certain workflows (such as prisma generate) to proceed even when URLs are undefined.
#28903: feat(cli): customize prisma init based on the JS runtime (Bun vs others)
- Makes prisma init tailor generated setup depending on whether the runtime is Bun or another JavaScript runtime.
#28846: fix(client-engine-runtime): make DataMapperError a UserFacingError
- Ensures DataMapperError is surfaced as a user-facing error for clearer, more actionable error reporting.
#28849: fix(adapter-{pg,neon,ppg}): handle 22P02 error in Postgres
- Improves Postgres adapter error handling for invalid-text-representation errors (22P02).
#28913: fix: fix byte upserts by removing legacy byte array representation
- Fixes byte upsert behavior by removing a legacy byte-array representation path.
#28535: fix(client,internals,migrate,generator-helper): handle multibyte UTF-8 characters split across chunk boundaries in byline
- Prevents issues when multibyte UTF-8 characters are split across chunk boundaries during line processing.
#28911: fix(cli): make prisma version --json emit JSON only to stdout
- Ensures machine-readable JSON output is emitted cleanly to stdout without extra noise.

VS Code Extension

#1950: fix: TML-1670 studio connections
- Resolves issues related to Studio connections, improving reliability for VS Code or language-server integrations.

Open roles at Prisma

Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [Careers page](https://www.prisma.io/careers#current) and find the role that’s right for you.

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.

7.1.0

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

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

This release brings quality of life improvements and fixes various bugs.

Prisma ORM

#28735: pnpm monorepo issues with prisma client runtime utils
Resolves issues in pnpm monorepos where users would report TypeScript issues related to @prisma/client-runtime-utils.
#28769: implement sql commenter plugins for Prisma Client
This PR implements support for SQL commenter plugins to Prisma Client. The feature will allow users to add metadata to SQL queries as comments following the sqlcommenter format.

Here’s two related PRs that were also merged:
- #28796: implement query tags for SQL commenter plugin
- #28802: add traceContext SQL commenter plugin
#28737: added error message when constructing client without configs
This commit adds an additional error message when trying to create a new PrismaClient instance without any arguments.
Thanks to @xio84 for this community contribution!
#28820: mark @opentelemetry/api as external in instrumentation
Ensures @opentelemetry/api is treated as an external dependency rather than bundled.
Since it is a peer dependency, this prevents applications from ending up with duplicate copies of the package.
#28694: allow env() helper to accept interface-based generics
Updates the env() helper’s type definition so it works with interfaces as well as type aliases.
This removes the previous constraint requiring an index signature and resolves TS2344 errors when using interface-based env types. Runtime behavior is unchanged.
Thanks to @SaubhagyaAnubhav for this community contribution!

Read Replicas extension

#53: Add support for Prisma 7
Users of the read-replicas extension can now use the extension in Prisma v7. You can update by installing:
```
npm install @prisma/extension-read-replicas@latest
```
For folks still on Prisma v6, install version 0.4.1:
```
npm install @prisma/extension-read-replicas@0.4.1
```

For more information, visit the repo

SQL comments

We're excited to announce SQL Comments support in Prisma 7.1.0! This new feature allows you to append metadata to your SQL queries as comments, making it easier to correlate queries with application context for improved observability, debugging, and tracing.

SQL comments follow the sqlcommenter format developed by Google, which is widely supported by database monitoring tools. With this feature, your SQL queries can include rich metadata:

SELECT "id", "name" FROM "User" /*application='my-app',traceparent='00-abc123...-01'*/

Basic usage

Pass an array of SQL commenter plugins to the new comments option when creating a PrismaClient instance:

import { PrismaClient } from './generated/prisma/client';
import { PrismaPg } from '@prisma/adapter-pg';
import { queryTags } from '@prisma/sqlcommenter-query-tags';
import { traceContext } from '@prisma/sqlcommenter-trace-context';

const adapter = new PrismaPg({
  connectionString: `${process.env.DATABASE_URL}`,
});

const prisma = new PrismaClient({
  adapter,
  comments: [queryTags(), traceContext()],
});

Query tags

The @prisma/sqlcommenter-query-tags package lets you add arbitrary tags to queries within an async context:

import { queryTags, withQueryTags } from '@prisma/sqlcommenter-query-tags';

const prisma = new PrismaClient({
  adapter,
  comments: [queryTags()],
});

// Wrap your queries to add tags
const users = await withQueryTags(
  { route: '/api/users', requestId: 'abc-123' },
  () => prisma.user.findMany(),
);

Resulting SQL:

SELECT ... FROM "User" /*requestId='abc-123',route='/api/users'*/

Use withMergedQueryTags to merge tags with outer scopes:

import {
  withQueryTags,
  withMergedQueryTags,
} from '@prisma/sqlcommenter-query-tags';

await withQueryTags({ requestId: 'req-123', source: 'api' }, async () => {
  await withMergedQueryTags(
    { userId: 'user-456', source: 'handler' },
    async () => {
      // Queries here have: requestId='req-123', userId='user-456', source='handler'
      await prisma.user.findMany();
    },
  );
});

Trace context

The @prisma/sqlcommenter-trace-context package adds W3C Trace Context (traceparent) headers for distributed tracing correlation:

import { traceContext } from '@prisma/sqlcommenter-trace-context';

const prisma = new PrismaClient({
  adapter,
  comments: [traceContext()],
});

When tracing is enabled and the span is sampled:

SELECT * FROM "User" /*traceparent='00-0af7651916cd43dd8448eb211c80319c-b9c7c989f97918e1-01'*/

Note: Requires @prisma/instrumentation to be configured. The traceparent is only added when tracing is active and the span is sampled.

Custom plugins

Create your own plugins to add custom metadata:

import type { SqlCommenterPlugin } from '@prisma/sqlcommenter';

const applicationTags: SqlCommenterPlugin = (context) => ({
  application: 'my-service',
  environment: process.env.NODE_ENV ?? 'development',
  operation: context.query.action,
  model: context.query.modelName,
});

const prisma = new PrismaClient({
  adapter,
  comments: [applicationTags],
});

Framework integration

SQL comments work seamlessly with popular frameworks, e.g., Hono:

import { createMiddleware } from 'hono/factory';
import { withQueryTags } from '@prisma/sqlcommenter-query-tags';

app.use(
  createMiddleware(async (c, next) => {
    await withQueryTags(
      {
        route: c.req.path,
        method: c.req.method,
        requestId: c.req.header('x-request-id') ?? crypto.randomUUID(),
      },
      () => next(),
    );
  }),
);

Additional framework examples for Express, Koa, Fastify, and NestJS are available in the documentation.

For complete documentation, see SQL Comments. We'd love to hear your feedback on this feature! Please open an issue on GitHub or join the discussion in our Discord community.

Open roles at Prisma

Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our Careers page and find the role that’s right for you.

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.

7.0.1

Today, we are issuing a 7.0.1 patch release focused on quality of life improvements, and bug fixes.

🛠 Fixes

Prisma Studio:
- Support Deno >= 1.4 <2.2 and Bun >= 1 (via https://github.com/prisma/prisma/pull/28583)
- Fix collisions between user and internal Studio columns when querying (via https://github.com/prisma/prisma/pull/28677)
- Warn when SQLite file doesn't exist (via https://github.com/prisma/prisma/pull/28711/commits/c33a1ea9e5a94e6a5c876bc4567915cc5f354658)
- Fix https://github.com/prisma/studio/issues/1363 (via https://github.com/prisma/prisma/pull/28711/commits/07224d4651d043f4b08735eeaa144aa9d75f9fe3)
- Sort tables alphabetically (via https://github.com/prisma/prisma/pull/28702)
Prisma CLI
- Fix potential vulnerabilities in installed dependencies (via https://github.com/prisma/prisma/pull/28592)
- Fix https://github.com/prisma/prisma/issues/28240, an exit code regression affecting prisma migrate diff (via https://github.com/prisma/prisma-engines/pull/5699)
- Show informative message when prisma db seed is run, but no migrations.seed command is specified in the Prisma config file (via https://github.com/prisma/prisma/pull/28711)
- Relax engines check in package.json, to let Node.js 25+ users adopt Prisma, although Node.js 25+ isn't considered stable yet (via https://github.com/prisma/prisma/pull/28600). Thanks @Sajito!
Prisma Client
- Restore cockroachdb support in prisma-client-js generator, after it was accidentally not shipped in Prisma 7.0.0 (via https://github.com/prisma/prisma/pull/28690)
@prisma/better-sqlite3
- Bump underlying version of better-sqlite3 to ^12.4.5, fixing https://github.com/prisma/prisma/issues/28624 (via https://github.com/prisma/prisma/pull/28625). Thank you @bhbs!

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

ESM Prisma Client as the default

The Rust-free/ESM 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
Significantly simpler deployments

Adopting the new 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"
}

Prisma Client changes

In v7, we've moved to requiring users pass either an adapter or accelerteUrl when creating a new instance of PrismaClient.

For Driver Adapters

import { PrismaClient } from './generated/prisma/client';
import { PrismaPg } from '@prisma/adapter-pg';

const adapter = new PrismaPg({ 
  connectionString: process.env.DATABASE_URL 
});
const prisma = new PrismaClient({ adapter });

For other databases:

// If using SQLite
import { PrismaBetterSqlite3 } from '@prisma/adapter-better-sqlite3';
const adapter = new PrismaBetterSqlite3({
  url: process.env.DATABASE_URL || 'file:./dev.db'
})

// If using MySql
import { PrismaMariaDb } from '@prisma/adapter-mariadb';
const adapter = new PrismaMariaDb({
  host: "localhost",
  port: 3306,
  connectionLimit: 5
});

We’ve also removed support for additional options when configuring your Prisma Client

new PrismaClient({ datasources: .. }) support has been removed
new PrismaClient({datasourceUrl: ..}) support has been removed
new PrismaClient() support has been removed
new PrismaClient({}) support has been removed

For Prisma Accelerate users:

import { PrismaClient } from "./generated/prisma/client"
import { withAccelerate } from "@prisma/extension-accelerate"

const prisma = new PrismaClient({
  accelerateUrl: process.env.DATABASE_URL,
}).$extends(withAccelerate())

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';

For developers who still need to stay on the prisma-client-js but are using the new output option, theres’s a new required package, @prisma/client-runtime-utils , which needs to be installed:

# for prisma-client-js users only
npm install @prisma/client-runtime-utils

Removal of implicit Prisma commands

In previous releases, Prisma would run generate and seed in various situations:

post-install hook would run prisma generate
prisma migrate would run prisma generate and prisma seed

This behaviour has been removed in favor of explicitly requiring commands to be run by users.

Removal of `prisma generate` flags

For prisma generate , we’ve removed a few flags that were no longer needed:

prisma generate --data-proxy
prisma generate --accelerate
prisma generate --no-engine
prisma generate --allow-no-models

Removal of `prisma db` flags

For prisma db, we’ve removed the following flag:

prisma db pull --local-d1
This parameter no longer exists but equivalent functionality can be implemented by defining a config file with a connection string for the local D1 database. We provide a helper function listLocalDatabases in the D1 adapter to simplify the migration:

import { defineConfig } from '@prisma/config'
import { listLocalDatabases } from '@prisma/adapter-d1'

export default defineConfig({
  datasource: {
    url: `file://${listLocalDatabases().pop()}`,
  },
})

Removal of `prisma migrate` flags

For prisma migrate diff, we’ve removed the following flags:

prisma --[from/to]-schema-datamodel
- This is now replaced with just --[from/to]-schema. The usage is otherwise the same.
prisma --[from/to]-url, prisma --[from/to]-schema-datasource
- These are now replaced with --[from/to]-config-datasource. The user is expected to populate the datasource in the config file and use the new flag. We no longer support diffing two different URLs/datasources, since only one config can be used at a time.
prisma --[from/to]-local-d1
- These are now replaced with --[from/to]-config-datasource. The user is expected to populate the datasource in the config file and use the new flag with a minor complication due to the fact that it needs to reference the local D1 database. Our listLocalDatabases helper function can be used for that, analogously to the db pull --local-d1 example above (where the user sets the datasource URL to file://${listLocalDatabases().pop()})

MongoDB support in Prisma 7

Currently, MongoDB is not supported in Prisma 7. For folks using MongoDB, please stay on Prisma v6. We aim to add support for MongoDB in a future release.

Driver Adapter naming updates

We’ve standardized our naming conventions for the various driver adapters internally. The following driver adapters have been updated:

PrismaBetterSQLite3 ⇒ PrismaBetterSqlite3
PrismaD1HTTP ⇒ PrismaD1Http
PrismaLibSQL ⇒ PrismaLibSql
PrismaNeonHTTP ⇒ PrismaNeonHttp

Schema and config file updates

As part of a larger change in how the Prisma CLI reads your project configuration, we’ve updated what get’s set the schema, and what gets set in the prisma.config.ts . Also as part of this release, prisma.config.ts is now required for projects looking to perform introspection and migration.

Schema changes

datasource.url is now configured in the config file
datasource.shadowDatabaseUrl is now configured in the config file
datasource.directUrl has been made unnecessary and has removed
generator.runtime=”react-native” has been removed

For early adopters of the config file, a few things have been removed with this release

engine: 'js'| 'classic' has been removed
adapter has been removed

A brief before/after:

// schema.prisma
datasource db {
  provider = "postgresql"
  url = ".."
  directUrl = ".."
  shadowDatabaseUrl = ".."
}

// ./prisma.config.ts
export default defineConfig({
  datasource: {
    url: '..',
    shadowDatabaseUrl: '..',
  }
})

Explicit loading of environment variables

As part of the move to Prisma config, we’re no longer automatically loading environment variables when invoking the Prisma CLI. Instead, developers can utilize libraries like dotenv to manage their environment variables and load them as they need. This means you can have dedicated local environment variables or ones set only for production. This removes any accidental loading of environment variables while giving developers full control.

Removed support for `prisma` keyword in `package.json`

In previous releases, users could configure their schema entry point and seed script in a prisma block in the package.json of their project. With the move to prisma.config.ts, this no longer makes sense and has been removed. To migrate, use the Prisma config file instead:

{
  "name": "my-project",
  "version": "1.0.0",
  "prisma": {
    "schema": "./custom-path-to-schema/schema.prisma",
    "seed": "tsx ./prisma/seed.ts"
  }
}

import 'dotenv/config'
import { defineConfig, env } from "prisma/config";
export default defineConfig({
  schema: "prisma/schema.prisma",
  migrations: {
      seed: "tsx prisma/seed.ts"
  },
  datasource: {...},
});

Removed Client Engines:

We’ve removed the following client engines:

LibraryEngine (engineType = "library", the Node-API Client)
BinaryEngine (engineType = "binary", the long-running executable binary)
DataProxyEngine and AccelerateEngine (Accelerate uses a new RemoteExecutor now)
ReactNativeEngine

Deprecated metrics feature has been removed

We deprecated the previewFeature metrics some time ago, and have removed it fully for version 7. If you need metrics related data available, you can use the underlying driver adapter itself, like the Pool metric from the Postgres driver.

Miscellaneous

#28493: Stop shimming WeakRef in Cloudflare Workers. This will now avoid any unexpected memory leaks.
#28297: Remove hardcoded URL validation. Users are now required to make sure they don’t include sensitive information in their config files.
#28273: Removed Prisma v1 detection
#28343: Remove undocumented --url flag from prisma db pull
#28286: Remove deprecated prisma introspect command.
#28480: Rename /wasm to /edge
- This change only affects prisma-client-js
- Before:
  - /edge → meant “for Prisma Accelerate”
  - /wasm → meant “for Edge JS runtimes (e.g., Cloudflare, Vercel Edge)”
- After:
  - /edge → means “for Edge JS runtimes (e.g., Cloudflare, Vercel Edge)”
The following Prisma-specific environment variables have been removed
- PRISMA_CLI_QUERY_ENGINE_TYPE
- PRISMA_CLIENT_ENGINE_TYPE
- PRISMA_QUERY_ENGINE_BINARY
- PRISMA_QUERY_ENGINE_LIBRARY
- PRISMA_GENERATE_SKIP_AUTOINSTALL
- PRISMA_SKIP_POSTINSTALL_GENERATE
- PRISMA_GENERATE_IN_POSTINSTALL
- PRISMA_GENERATE_DATAPROXY
- PRISMA_GENERATE_NO_ENGINE
- PRISMA_CLIENT_NO_RETRY
- PRISMA_MIGRATE_SKIP_GENERATE
- PRISMA_MIGRATE_SKIP_SEED

Mapped enums

If you followed along on twitter, you will have seen that we teased a highly-request user feature was coming to v7.0. That highly-requested feature is…. mapped emuns! We now support the @map attribute for enum members, which can be used to set their expected runtime values

enum PaymentProvider {
  MixplatSMS    @map("mixplat/sms")
  InternalToken @map("internal/token")
  Offline       @map("offline")

  @@map("payment_provider")
}

export const PaymentProvider: {
  MixplatSMS: 'mixplat/sms'
  InternalToken: 'internal/token'
  Offline: 'offline'
}

New Prisma Studio comes to the CLI

We launched a new version of Prisma Studio to our Console and VS Code extension a while back, but the Prisma CLI still shipped with the older version.

Now, with v7.0, we’ve updated the Prisma CLI to include the new Prisma Studio. Not only are you able to inspect your database, but you get rich visualization to help you understand connected relationships in your database. It’s customizable, much smaller, and can inspect remote database by passing a --url flag. This new version of Prisma Studio is not tied to the Prisma ORM, and establishes a new foundation for what comes next.

Currently, the new studio only supports Postgres, MySQL, and SQLite, with support for other databases coming in a future release.

For issues related to Prisma Studio, please direct them to the Studio repo on github.

Prisma Postgres

Prisma Postgres is our managed Postgres service, designed with the same philosophy of great DX that has guided Prisma for close to a decade. It works great with serverless, it’s fast, and with simple pricing and a generous free tier. Here’s what’s new:

Connection Pooling Changes with Prisma Accelerate

With support for connection pooling being added natively to Prisma Postgres, Prisma Accelerate now serves as a dedicated caching layer. If you were using Accelerate for the connection pooling features, don’t worry! Your existing connection string via Accelerate will continue to work, and you can switch to the new connection pool when you’re ready.

Simplified connection flow

We've made connecting to Prisma Postgres even simpler. Now, when you go to connect to a database, you’ll get new options to enable connection pooling, or to enable Prisma Accelerate for caching. Below, you’ll get code snippets for getting things configured in your project right away.

Serverless driver

For those who want to connect to Prisma Postgres but are deploying to environments like Cloudflare Workers, we have a new version of the serverless client library to support these runtimes.

Compatible with Cloudflare Workers, Vercel Edge Functions, Deno Deploy, AWS Lambda, and Bun
Stream results row-by-row to handle large datasets with constant memory usage
Pipeline multiple queries over a single connection, reducing latency by up to 3x
SQL template literals with automatic parameterization and full TypeScript support
Built-in transactions, batch operations, and extensible type system

Check out the serverless driver docs for more details

Open roles at Prisma

Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our Careers page and find the role that’s right for you.

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.9.0

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

🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.

Highlights

Prisma ORM without Rust engines for PostgreSQL & SQLite (Preview)

If you've been excited about our work of removing the Rust engines from Prisma ORM but hesitated trying it out because it was in an Early Access (EA) phase, now is a great time for you to get your hands on the Rust-free Prisma ORM version.

This major architectural change has moved from EA into Preview in this release, meaning there are no more know major issues. If you want to try it out, add the queryCompiler and driverAdapters preview feature flags to your generator, install the driver adapter for your database, and get going:

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

Now run prisma generate to re-generate Prisma Client. If you didn't use a driver adapter before, you'll need to install, e.g. the one for PostgreSQL:

npm install @prisma/adapter-pg

Once installed, you can instantiate PrismaClient as follows:

import { PrismaClient } from './generated/prisma'
import { PrismaPg } from '@prisma/adapter-pg'

const adapter = new PrismaPg({ connectionString: env.DATABASE_URL })
const prisma = new PrismaClient({ adapter })

No more hassle with query engines, binary targets and an even smoother experience in serverless and edge environments!

📚 Learn more in the docs.

Major improvements for local Prisma Postgres (Preview)

In the last release, we enabled you to spin up a Prisma Postgres instance locally via the new prisma dev command. Local Prisma Postgres uses PGlite under the hood and gives you an identical experience as you get with a remote Prisma Postgres instance.

This release brings major improvements to this feature:

Persists your databases across prisma dev invocations.
Enables you to have multiple local Prisma Postgres instances running at the same time.
Running prisma init now uses local Prisma Postgres by default.

Try it out and let us know what you think!

📚 Learn more in the docs.

More news

Connect to Prisma Postgres with any ORM (Preview)

Since its GA release, you could only interact with Prisma Postgres using Prisma ORM via a custom connection string.

This has changed now: When setting up a new Prisma Postgres instance, you receive a regular PostgreSQL direct TCP connection string (starting with postgres://...) that lets you connect to it using your favorite tool or database library, including Drizzle, Kysely, TypeORM, and others.

If you want to access Prisma Postgres from a serverless environment, you can also use our new serverless driver (Early Access).

📚 Learn more in the docs.

Automated backup & restore

Prisma Postgres' backup and restore mechanism has seen a major upgrade recently: You can now easily restore any previous backup via the UI in the Prisma Console. Find the new Backups tab when viewing your database and select any backup from the list to restore its state to a previous point in time.

📚 Learn more in the docs.

Prisma's VS Code extension now has a UI to manage Prisma Postgres

If you're using Prisma ORM, chances are that you're using our VS Code extension too. In its latest release, we've added a major new capability to it: A UI for managing databases.

With this new UI, you can:

Authenticate with the Prisma Console
Create and delete remote Prisma Postgres instances
View local Prisma Postgres instances
View and edit data via an embedded Prisma Studio
Visualize your database schema

To use the new features, make sure to have the latest version of the Prisma VS Code extension installed and look out for the new Prisma logo in VS Code's Activity Bar.

📚 Learn more in the docs.

New region for Prisma Postgres: San Francisco (`us-west-1`)

We keep expanding Prisma Postgres availability across the globe! After having added Singapore just a few weeks ago, we're now adding San Francisco based on another poll we ran on X. Here are all the regions where you can spin up Prisma Postgres instances today:

us-west-1: San Francisco (new!)
us-east-1: North Virginia
eu-west-3: Paris
ap-northeast-1: Tokyo
ap-southeast-1: Singapore

Keep an eye on our X account to take part in the poll and vote for the next availability zone of Prisma Postgres!

6.8.2

Today, we are issuing the 6.8.2 patch release. It fully resolves an issue with the prisma init and prisma dev commands for some Windows users who were still facing problems after the previous incomplete fix in version 6.8.1.

Fixes:

https://github.com/prisma/prisma/issues/27195

6.8.1

Today, we are issuing the 6.8.1 patch release. It fixes an issue with the prisma init and prisma dev commands on Windows.

Fixes

https://github.com/prisma/prisma/issues/27192

6.8.0

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 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:

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:

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.

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 generator:

generator client {
  provider = "prisma-client"
  output   = "../src/generated/prisma"
  runtime = "deno"
}

📚 Learn more in the docs.

VS Code Agent Mode: AI support with your database workflows

Have you tried agent mode in VS Code 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 and your agent is ready to go 🚀

📚 Learn more in the docs.

Other news

You voted, we acted: New Singapore region for Prisma Postgres

We recently ran a poll 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 for another poll asking for your favorite regions that we should add!

6.7.0

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

🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release.

Highlights

Prisma ORM without Rust engines (Early Access)

If you're a regular visitor of our company blog, you may already know that we're currently working on moving the core of Prisma from Rust to TypeScript. We have written extensively about why we're moving away from Rust and already shared the first measurements of performance boosts we saw from the re-write.

This re-write is not just a move from one programming language to another. It fundamentally improves the architecture of Prisma ORM and replaces the Query Engine (which is written in Rust and deployed as a standalone binary) with a much leaner and more efficient approach that we call Query Compiler.

In this release, we're excited to give you Early Access to the new Query Compiler for PostgreSQL and SQLite database 🥳 Support for more database will follow very soon!

To use the new "Rust-free" version of Prisma ORM, add the queryCompiler (new) and driverAdapters feature flags to your client generator:

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

Now run prisma generate to re-generate Prisma Client. If you didn't use a driver adapter before, you'll need to install one. For example, the one for PostgreSQL:

npm install @prisma/adapter-pg

Once installed, you can instantiate PrismaClient as follows:

import { PrismaPg } from '@prisma/adapter-pg'
import { PrismaClient } from './generated/prisma'

const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL })
const prisma = new PrismaClient({ adapter })

This version of PrismaClient doesn't have a Query Engine binary and you can use it in the exact same way as before.

📚 Learn more in the docs.

Support for `better-sqlite3` JavaScript driver (Preview)

Driver adapters are Prisma ORM's way of letting you use JS-native drivers (like pg) to interact with your database. In this release, we're introducing a new driver adapter for using the better-sqlite3 package, so you can now interact with SQLite database in a JS-native way.

To use it, first enable the driverAdapters Preview feature flag in on your client generator, then install these libraries:

npm install @prisma/adapter-better-sqlite3

Now you can instantiate Prisma Client as follows:

import { PrismaBetterSQLite3 } from '@prisma/adapter-better-sqlite3';
import { PrismaClient } from './generated/prisma';

const adapter = new PrismaBetterSQLite3({
  url: "file:./prisma/dev.db"
});
const prisma = new PrismaClient({ adapter });

📚 Learn more in the docs.

Multi-file Prisma schemas are now production-ready

The prismaSchemaFolder Preview feature is moving into General Availability 🎉 With that change, Prisma ORM now by default supports splitting your Prisma schema file and e.g. lets you organize your schema as follows:

prisma/schema.prisma → defines data source and generator

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
}

prisma/models/posts.prisma → defines Post model

model Post {
  id        Int     @id @default(autoincrement())
  title     String
  content   String?
  published Boolean @default(false)
  author    User?   @relation(fields: [authorId], references: [id])
  authorId  Int?
}

prisma/models/users.prisma → defines User model

model User {
  id    Int     @id @default(autoincrement())
  email String  @unique
  name  String?
  posts Post[]
}

⚠️ Note that there have been breaking changes to the prismaSchemaFolder Preview feature in the last 6.6.0 release. If you've been using this feature to split your Prisma schema, make sure to read the release notes and update your project accordingly.

📚 Learn more in the docs.

Splitting generated output with new `prisma-client` generator (Preview)

With the prisma-client-js generator, the generated Prisma Client library is put into a single index.d.ts file. This sometimes led to issues with large schemas where the size of the generated output could slow down code editors and breaking auto-complete.

As of this release, our new prisma-client generator (that was released in 6.6.0) now splits the generated Prisma Client library into multiple files and thus avoids the problems of a single, large output file.

Also: As a bonus, we now ensure that generated files do not raise any ESLint and TypeScript errors!

Before

generated/
└── prisma
    ├── client.ts
    ├── index.ts # -> this is split into multiple files in 6.7.0
    └── libquery_engine-darwin.dylib.node

After

generated/
└── prisma
    ├── client.ts
    ├── commonInputTypes.ts
    ├── enums.ts
    ├── index.ts
    ├── internal
    │   ├── class.ts
    │   └── prismaNamespace.ts
    ├── libquery_engine-darwin.dylib.node
    ├── models
    │   ├── Post.ts
    │   └── User.ts
    └── models.ts

📚 Learn more in the docs.

Company news

Our team has been busy shipping more than just the ORM! Check out these articles to learn what else we've been up to recently:

6.6.0

Today, we are excited to share the 6.6.0 stable release 🎉 This version comes packed with exciting features, we can't wait to see what you're going to build with it! Read our announcement blog post for more details: Prisma ORM 6.6.0: ESM Support, D1 Migrations & MCP Server

🌟 Help us spread the word about Prisma by starring the repo ☝️ or posting on X about the release. 🌟

Highlights

ESM support with more flexible `prisma-client` generator (Early Access)

We are excited to introduce a new prisma-client generator that's more flexible, comes with ESM support and removes any magic behaviours that may cause friction with the current prisma-client-js generator.

Note

: The prisma-client generator is currently in Early Access and will likely have some breaking changes in the next releases.

Here are the main differences:

Requires an output path; no “magic” generation into node_modules any more
Supports ESM and CommonJS via the moduleFormat field
Outputs plain TypeScript that's bundled just like the rest of your application code

Here's how you can use the new prisma-client generator in your Prisma schema:

// prisma/schema.prisma
generator client {
  provider     = "prisma-client"           // no `-js` at the end
  output       = "../src/generated/prisma" // `output` is required
  moduleFormat = "esm"                     // or `"cjs"` for CommonJS
}

In your application, you can then import the PrismaClient constructor (and anything else) from the generated folder:

// src/index.ts
import { PrismaClient } from './generated/prisma/client'

⚠️ Important: We recommend that you add the output path to .gitignore so that the query engine that's part of the generated Prisma Client is kept out of version control:

# .gitignore
./src/generated/prisma

📚 Learn more in the docs.

Cloudflare D1 & Turso/LibSQL migrations (Early Access)

Cloudflare D1 and Turso are popular database providers that are both based on SQLite. While you can query them using the respective driver adapter for D1 or Turso, previous versions of Prisma ORM weren't able to make schema changes against these databases.

With today's release, we're sharing the first Early Access version of native D1 migration support for the following commands:

prisma db push: Updates the schema of the remote database based on your Prisma schema
prisma db pull: Introspects the schema of the remote database and updates your local Prisma schema
prisma migrate diff: Outputs the difference between the schema of the remote database and your local Prisma schema

Note

: Support for prisma migrate dev and prisma migrate deploy will come very soon!

To use these commands, you need to connect the Prisma CLI to your D1 or Turso instance by using the driver adapter in your prisma.config.ts file. Here is an example for D1:

import path from 'node:path'
import type { PrismaConfig } from 'prisma'
import { PrismaD1HTTP } from '@prisma/adapter-d1'

// import your .env file
import 'dotenv/config'

type Env = {
  CLOUDFLARE_D1_TOKEN: string
  CLOUDFLARE_ACCOUNT_ID: string
  CLOUDFLARE_DATABASE_ID: string
}

export default {
  earlyAccess: true,
  schema: path.join('prisma', 'schema.prisma'),

  migrate: {
    async adapter(env) {
      return new PrismaD1HTTP({
        CLOUDFLARE_D1_TOKEN: env.CLOUDFLARE_D1_TOKEN,
        CLOUDFLARE_ACCOUNT_ID: env.CLOUDFLARE_ACCOUNT_ID,
        CLOUDFLARE_DATABASE_ID: env.CLOUDFLARE_DATABASE_ID,
      })
    },
  },
} satisfies PrismaConfig<Env>

With that setup, you can now execute schema changes against your D1 instance by running:

npx prisma db push

📚 Learn more in the docs:

MCP server to manage Prisma Postgres via LLMs (Preview)

Prisma Postgres is the first serverless database without cold starts. Designed for optimal efficiency and high performance, it's the perfect database to be used alongside AI tools like Cursor, Windsurf, Lovable or co.dev. In this ORM release, we're adding a command to start a Prisma MCP server that you can integrate in your AI development environment. Thanks to that MCP server, you can now:

tell your AI agent to create new DB instances
design your data model
chat through a database migration

… and much more.

To get started, add this snippet to the MCP configuration of your favorite AI tool and get started:

{
  "mcpServers": {
    "Prisma": {
      "command": "npx",
      "args": ["-y", "prisma", "mcp"]
    }
  }
}

📚 Learn more in the docs.

New `--prompt` option on `prisma init`

You can now pass a --prompt option to the prisma init command to have it scaffold a Prisma schema for you and deploy it to a fresh Prisma Postgres instance:

npx prisma init --prompt "Simple habit tracker application"

For everyone, following social media trends, we also created an alias called --vibe for you 😉

npx prisma init --vibe "Cat meme generator"

Improved API for using driver adapters

In this release, we are introducing a nice DX improvement for driver adapters. Driver adapters let you access your database using JS-native drivers with Prisma ORM.

Before 6.6.0

Earlier versions of Prisma ORM required you to first instantiate the driver itself, and then use that instance to create the Prisma driver adapter. Here is an example using the @libsql/client driver for LibSQL:

import { createClient } from '@libsql/client'
import { PrismaLibSQL } from '@prisma/adapter-libsql'
import { PrismaClient } from '@prisma/client'

// Old way of using driver adapters (before 6.6.0)
const driver = createClient({
  url: env.LIBSQL_DATABASE_URL,
  authToken: env.LIBSQL_DATABASE_TOKEN,
})
const adapter = new PrismaLibSQL(driver)

const prisma = new PrismaClient({ adapter })

6.6.0 and later

As of this release, you instantiate the driver adapter directly with the options of your preferred JS-native driver.:

import { PrismaLibSQL } from '@prisma/adapter-libsql'
import { PrismaClient } from '../prisma/prisma-client'

const adapter = new PrismaLibSQL({
  url: env.LIBSQL_DATABASE_URL,
  authToken: env.LIBSQL_DATABASE_TOKEN,
})

const prisma = new PrismaClient({ adapter })

Other changes

`prismaSchemaFolder` breaking changes

If you are using the prismaSchemaFolder Preview feature to split your Prisma schema into multiple files, you may encounter some breaking changes in this version.

Explicit declaration of schema folder location

You now must always provide the path to the schema folder explicitly. You can do this in either of three ways:

pass the the --schema option to your Prisma CLI command (e.g. prisma migrate dev --schema ./prisma/schema)

set the prisma.schema field in package.json:

// package.json
{
  "prisma": {
    "schema": "./schema"
  }
}

set the schema property in prisma.config.ts:

import path from 'node:path'
import type { PrismaConfig } from 'prisma'

export default {
  earlyAccess: true,
  schema: path.join('prisma', 'schema'),
} satisfies PrismaConfig<Env>

`migrations` folder must live next to `.prisma` file with `datasource` block

Your migrations directory must live next to the .prisma file that defines your datasource blog. If you relied on the implicit schema folder location of ./prisma/schema make sure to move your migrations folder from ./prisma/migrations to ./prisma/schema/migrations.

Assuming schema.prisma defines the datasource in this example, here's how how need to place the migrations folder:

# `migrations` and `schema.prisma` are on the same level
.
├── migrations
├── models
│   ├── posts.prisma
│   └── users.prisma
└── schema.prisma

See this PR for more details.

No more Bun issues if Node.js is not installed

Bun users reported an issue that prisma generate would hang if Node.js installed on their machine. This is now fixed and Bun users can generate Prisma Client without issues.

Company news

Enterprise support

Prisma offers an enterprise support plan for Prisma ORM. Get direct help from our team and a joint slack channel! With Prisma ORM 7 on the horizon, this is a great time to upgrade your support today.

We are hiring: Developer Support Engineer

If you care about making developers successful, join us as a Developer Support Engineer.

6.5.0

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

🌟 Help us spread the word about Prisma by starring the repo ☝️ or tweeting about the release. 🌟

Highlights

Databases can only be reset manually and explicitly

In previous versions, if Prisma ORM determined that a migrate command could not be applied cleanly to the underlying database, you would get a message like this one:

? We need to reset the "public" schema at "db.url.com:5432"
Do you want to continue? All data will be lost. (y/N)

While "no" was the default, we've determined that having this prompt in the first place was a mistake. In this version we're removing the prompt entirely and instead exiting with an appropriate error message.

To get the previous behavior, you will need to run prisma migrate reset directly.

Support for `prisma.config.ts` in Prisma Studio

We've expanded support for our prisma.config.ts file to include Prisma Studio!

To use the new config file, including the ability to connect to driver adapter enabled databases with Prisma Studio, add a studio block to your prisma.config.ts file:

import path from 'node:path'
import type { PrismaConfig } from 'prisma'
import { PrismaLibSQL } from '@prisma/adapter-libsql'
import { createClient } from '@libsql/client'

export default {
  earlyAccess: true,
  schema: {
    kind: 'single',
    filePath: './prisma/schema.prisma',
  },
  studio: {
    adapter: async (env: unknown) => {
      const connectionString = `file:./dev.db'
      const libsql = createClient({
        url: connectionString,
      })
      return new PrismaLibSQL(libsql)
    },
  },
} satisfies PrismaConfig

Notice how this looks a little different from last release! Instead of an @prisma/config package there’s now two different options:

Using the defineConfig helper exported by prisma/config.
Using the PrismaConfig utility type exported by Prisma.

All the relevant info for the prisma.config.ts file, including these new ways of defining your config, can be found in our docs.

Allow for chaining `$on` and `$extends`.

In previous versions of Prisma ORM, the return type of the $on client method was void. This did not allow for chaining $on() and $extends() calls, as $on is not available on extended clients.

In this version we've resolved this issue and $on will now return the modified Prisma Client.

Community fixes

We have a number of community-submitted fixes that improve Prisma ORM:

Allow for binaries to be loaded from local network. Thank you @RaHehl!
Enhance type safety of the AtLeast utility type. Thank you @de-novo!
Resolve a race condition in the NextJS monorepo plugin. Thank you @toniopelo!
allow for filtering out spans with PrismaInstrumentation. Thank you @overbit!

Prisma is hiring

Join us at Prisma and work on our TypeScript ORM (now faster than ever) and our Cloud products like Prisma Postgres (now in GA!)

We currently have two open roles in our Engineering team:

If these don’t fit, you can still check out our jobs page and send a general application.

Enterprise support

Prisma offers an enterprise support plan for Prisma ORM. Get direct help from our team and a joint slack channel! With Prisma ORM 7 on the horizon this is a great time to upgrade your support today.

Credits

Thank you to @overbit, @RaHehl, @toniopelo, and @de-novo for your contributions to this release!

✨ This PR was created by Minori, your friendly dependency updater! 🌸

## Dependency Update Updates **prisma** from `6.4.1` to `7.3.0`. ### Type devDependencies ### Changelog ## Changelog ### 7.3.0 Today, we are excited to share the `7.3.0` stable release 🎉 **🌟 Star this repo for notifications about new releases, bug fixes & features — or [follow us on X](https://pris.ly/x)!** ## ORM - [#28976](https://github.com/prisma/prisma/pull/28976): Fast and Small Query Compilers We've been working on various performance-related bugs since the initial ORM 7.0 release. With 7.3.0, we're introducing a new `compilerBuild` option for the client generator block in `schema.prisma` with two options: `fast` and `small`. This allows you to swap the underlying Query Compiler engine based on your selection, one built for speed (with an increase in size), and one built for size (with the trade off for speed). By default, the `fast` mode is used, but this can be set by the user: ```groovy generator client { provider = "prisma-client" output = "../src/generated/prisma" compilerBuild = "fast" // "fast" | "small" } ``` We still have more in progress for performance, but this new `compilerBuild` option is our first step toward addressing your concerns! - [#29005](https://github.com/prisma/prisma/pull/29005): Bypass the Query Compiler for Raw Queries Raw queries (`$executeRaw`, `$queryRaw`) can now skip going through the query compiler and query interpreter infrastructure. They can be sent directly to the driver adapter, removing additional overhead. - [#28965](https://github.com/prisma/prisma/pull/28965): Update MSSQL to v12.2.0 This community PR updates the `@prisma/adapter-mssql` to use MSSQL v12.2.0. Thanks [Jay-Lokhande](https://github.com/Jay-Lokhande)! - [#29001](https://github.com/prisma/prisma/pull/29001): Pin better-sqlite3 version to avoid SQLite bug An underlying bug in SQLite 3.51.0 has affected the `better-sqlite3` adapter. We’ve bumped the version that powers `@prisma/better-sqlite3` and have pinned the version to prevent any unexpected issues. If you are using `@prisma/better-sqlite3` , please upgrade to v7.3.0. - [#29002](https://github.com/prisma/prisma/pull/29002): Revert `@map` enums to v6.19.0 behavior In the initial release of v7.0, we made a change with Mapped Enums where the generated enum would get its value from the value passed to the `@map` function. This was a breaking change from v6 that caused issues for many users. We have reverted this change for the time being, as many different diverging approaches have emerged from the community discussion. - [prisma-engines#5745](https://github.com/prisma/prisma-engines/pull/5745): Cast BigInt to text in JSON aggregation When using `relationJoins` with BigInt fields in Prisma 7, JavaScript's `JSON.parse` loses precision for integers larger than `Number.MAX_SAFE_INTEGER` (2^53 - 1). This happens because PostgreSQL's `JSONB_BUILD_OBJECT` returns BigInt values as JSON numbers, which JavaScript cannot represent precisely. ``` // Original BigInt ID: 312590077454712834 // After JSON.parse: 312590077454712830 (corrupted!) ``` This PR cast BigInt columns to `::text` inside `JSONB_BUILD_OBJECT` calls, similar to how `MONEY` is already cast to `::numeric`. ``` -- Before JSONB_BUILD_OBJECT('id', "id") -- After JSONB_BUILD_OBJECT('id', "id"::text) ``` This ensures BigInt values are returned as JSON strings, preserving full precision when parsed in JavaScript. ## Open roles at Prisma Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [[Careers page](https://www.prisma.io/careers#current)](https://www.prisma.io/careers#current) and find the role that’s right for you. ## 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. ### 7.2.0 Today, we are excited to share the `7.2.0` stable release 🎉 **🌟 Star this repo for notifications about new releases, bug fixes & features — or [follow us on X](https://pris.ly/x)!** ## Highlights ## ORM - [#28830](https://github.com/prisma/prisma/pull/28830): feat: add `sqlcommenter-query-insights` plugin - Adds a new SQL commenter plugin to support query insights metadata. - [#28860](https://github.com/prisma/prisma/pull/28860): feat(migrate): add `-url` param for `db pull`, `db push`, `migrate dev` - Adds a `-url` flag to key migrate commands to make connection configuration more flexible. - [#28895](https://github.com/prisma/prisma/pull/28895): feat(config): allow undefined URLs in e.g. `prisma generate` - Allows certain workflows (such as `prisma generate`) to proceed even when URLs are undefined. - [#28903](https://github.com/prisma/prisma/pull/28903): feat(cli): customize `prisma init` based on the JS runtime (Bun vs others) - Makes `prisma init` tailor generated setup depending on whether the runtime is Bun or another JavaScript runtime. - [#28846](https://github.com/prisma/prisma/pull/28846): fix(client-engine-runtime): make `DataMapperError` a `UserFacingError` - Ensures `DataMapperError` is surfaced as a user-facing error for clearer, more actionable error reporting. - [#28849](https://github.com/prisma/prisma/pull/28849): fix(adapter-{pg,neon,ppg}): handle 22P02 error in Postgres - Improves Postgres adapter error handling for invalid-text-representation errors (`22P02`). - [#28913](https://github.com/prisma/prisma/pull/28913): fix: fix byte upserts by removing legacy byte array representation - Fixes byte upsert behavior by removing a legacy byte-array representation path. - [#28535](https://github.com/prisma/prisma/pull/28535): fix(client,internals,migrate,generator-helper): handle multibyte UTF-8 characters split across chunk boundaries in byline - Prevents issues when multibyte UTF-8 characters are split across chunk boundaries during line processing. - [#28911](https://github.com/prisma/prisma/pull/28911): fix(cli): make `prisma version --json` emit JSON only to stdout - Ensures machine-readable JSON output is emitted cleanly to stdout without extra noise. ## VS Code Extension - [#1950](https://github.com/prisma/language-tools/pull/1950): fix: TML-1670 studio connections - Resolves issues related to Studio connections, improving reliability for VS Code or language-server integrations. ## Open roles at Prisma Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [[Careers page](https://www.prisma.io/careers#current)](https://www.prisma.io/careers#current) and find the role that’s right for you. ## 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. ### 7.1.0 Today, we are excited to share the `7.1.0` stable release 🎉 **🌟 Star this repo for notifications about new releases, bug fixes & features — or [follow us on X](https://pris.ly/x)!** This release brings quality of life improvements and fixes various bugs. ## Prisma ORM - [#28735](https://github.com/prisma/prisma/pull/28735): **pnpm monorepo issues with prisma client runtime utils** Resolves issues in pnpm monorepos where users would report TypeScript issues related to `@prisma/client-runtime-utils`. - [#28769](https://github.com/prisma/prisma/pull/28769): **implement sql commenter plugins for Prisma Client** This PR implements support for SQL commenter plugins to Prisma Client. The feature will allow users to add metadata to SQL queries as comments following the [sqlcommenter format](https://google.github.io/sqlcommenter/). Here’s two related PRs that were also merged: - [#28796](https://github.com/prisma/prisma/pull/28796): **implement query tags for SQL commenter plugin** - [#28802](https://github.com/prisma/prisma/pull/28802): **add `traceContext` SQL commenter plugin** - [#28737](https://github.com/prisma/prisma/pull/28737): **added error message when constructing client without configs** This commit adds an additional error message when trying to create a new PrismaClient instance without any arguments. Thanks to @xio84 for this community contribution! - [#28820](https://github.com/prisma/prisma/pull/28820): **mark `@opentelemetry/api` as external in instrumentation** Ensures `@opentelemetry/api` is treated as an external dependency rather than bundled. Since it is a peer dependency, this prevents applications from ending up with duplicate copies of the package. - [#28694](https://github.com/prisma/prisma/pull/28694): **allow `env()` helper to accept interface-based generics** Updates the `env()` helper’s type definition so it works with interfaces as well as type aliases. This removes the previous constraint requiring an index signature and resolves TS2344 errors when using interface-based env types. Runtime behavior is unchanged. Thanks to @SaubhagyaAnubhav for this community contribution! ## Read Replicas extension - [#53](https://github.com/prisma/extension-read-replicas/pull/53): **Add support for Prisma 7** Users of the read-replicas extension can now use the extension in Prisma v7. You can update by installing: ```bash npm install @prisma/extension-read-replicas@latest ``` For folks still on Prisma v6, install version `0.4.1`: ```bash npm install @prisma/extension-read-replicas@0.4.1 ``` For more information, [visit the repo](https://github.com/prisma/extension-read-replicas) ## SQL comments We're excited to announce **SQL Comments** support in Prisma 7.1.0! This new feature allows you to append metadata to your SQL queries as comments, making it easier to correlate queries with application context for improved observability, debugging, and tracing. SQL comments follow the [sqlcommenter format](https://google.github.io/sqlcommenter/) developed by Google, which is widely supported by database monitoring tools. With this feature, your SQL queries can include rich metadata: ```sql SELECT "id", "name" FROM "User" /*application='my-app',traceparent='00-abc123...-01'*/ ``` ### Basic usage Pass an array of SQL commenter plugins to the new `comments` option when creating a `PrismaClient` instance: ```tsx import { PrismaClient } from './generated/prisma/client'; import { PrismaPg } from '@prisma/adapter-pg'; import { queryTags } from '@prisma/sqlcommenter-query-tags'; import { traceContext } from '@prisma/sqlcommenter-trace-context'; const adapter = new PrismaPg({ connectionString: `${process.env.DATABASE_URL}`, }); const prisma = new PrismaClient({ adapter, comments: [queryTags(), traceContext()], }); ``` ### Query tags The `@prisma/sqlcommenter-query-tags` package lets you add arbitrary tags to queries within an async context: ```tsx import { queryTags, withQueryTags } from '@prisma/sqlcommenter-query-tags'; const prisma = new PrismaClient({ adapter, comments: [queryTags()], }); // Wrap your queries to add tags const users = await withQueryTags( { route: '/api/users', requestId: 'abc-123' }, () => prisma.user.findMany(), ); ``` Resulting SQL: ```sql SELECT ... FROM "User" /*requestId='abc-123',route='/api/users'*/ ``` Use `withMergedQueryTags` to merge tags with outer scopes: ```tsx import { withQueryTags, withMergedQueryTags, } from '@prisma/sqlcommenter-query-tags'; await withQueryTags({ requestId: 'req-123', source: 'api' }, async () => { await withMergedQueryTags( { userId: 'user-456', source: 'handler' }, async () => { // Queries here have: requestId='req-123', userId='user-456', source='handler' await prisma.user.findMany(); }, ); }); ``` ### Trace context The `@prisma/sqlcommenter-trace-context` package adds W3C Trace Context (`traceparent`) headers for distributed tracing correlation: ```tsx import { traceContext } from '@prisma/sqlcommenter-trace-context'; const prisma = new PrismaClient({ adapter, comments: [traceContext()], }); ``` When tracing is enabled and the span is sampled: ```sql SELECT * FROM "User" /*traceparent='00-0af7651916cd43dd8448eb211c80319c-b9c7c989f97918e1-01'*/ ``` > Note: Requires @prisma/instrumentation to be configured. The traceparent is only added when tracing is active and the span is sampled. ### Custom plugins Create your own plugins to add custom metadata: ```tsx import type { SqlCommenterPlugin } from '@prisma/sqlcommenter'; const applicationTags: SqlCommenterPlugin = (context) => ({ application: 'my-service', environment: process.env.NODE_ENV ?? 'development', operation: context.query.action, model: context.query.modelName, }); const prisma = new PrismaClient({ adapter, comments: [applicationTags], }); ``` ### Framework integration SQL comments work seamlessly with popular frameworks, e.g., **Hono**: ```tsx import { createMiddleware } from 'hono/factory'; import { withQueryTags } from '@prisma/sqlcommenter-query-tags'; app.use( createMiddleware(async (c, next) => { await withQueryTags( { route: c.req.path, method: c.req.method, requestId: c.req.header('x-request-id') ?? crypto.randomUUID(), }, () => next(), ); }), ); ``` Additional framework examples for **Express**, **Koa**, **Fastify**, and **NestJS** are available in the documentation. For complete documentation, see [SQL Comments](https://www.prisma.io/docs/orm/prisma-client/observability-and-logging/sql-comments). We'd love to hear your feedback on this feature! Please open an issue on [GitHub](https://github.com/prisma/prisma) or join the discussion in our [Discord community](https://pris.ly/discord). ## Open roles at Prisma Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [Careers page](https://www.prisma.io/careers#current) and find the role that’s right for you. ## 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. ### 7.0.1 Today, we are issuing a 7.0.1 patch release focused on quality of life improvements, and bug fixes. ## 🛠 Fixes - **Prisma Studio**: - Support Deno >= 1.4 <2.2 and Bun >= 1 (via https://github.com/prisma/prisma/pull/28583) - Fix collisions between user and internal Studio columns when querying (via https://github.com/prisma/prisma/pull/28677) - Warn when SQLite file doesn't exist (via https://github.com/prisma/prisma/pull/28711/commits/c33a1ea9e5a94e6a5c876bc4567915cc5f354658) - Fix https://github.com/prisma/studio/issues/1363 (via https://github.com/prisma/prisma/pull/28711/commits/07224d4651d043f4b08735eeaa144aa9d75f9fe3) - Sort tables alphabetically (via https://github.com/prisma/prisma/pull/28702) - **Prisma CLI** - Fix potential vulnerabilities in installed dependencies (via https://github.com/prisma/prisma/pull/28592) - Fix https://github.com/prisma/prisma/issues/28240, an exit code regression affecting `prisma migrate diff` (via https://github.com/prisma/prisma-engines/pull/5699) - Show informative message when `prisma db seed` is run, but no `migrations.seed` command is specified in the Prisma config file (via https://github.com/prisma/prisma/pull/28711) - Relax `engines` check in `package.json`, to let Node.js 25+ users adopt Prisma, although Node.js 25+ isn't considered stable yet (via https://github.com/prisma/prisma/pull/28600). Thanks @Sajito! - **Prisma Client** - Restore `cockroachdb` support in `prisma-client-js` generator, after it was accidentally not shipped in Prisma 7.0.0 (via https://github.com/prisma/prisma/pull/28690) - **@prisma/better-sqlite3** - Bump underlying version of `better-sqlite3` to `^12.4.5`, fixing https://github.com/prisma/prisma/issues/28624 (via https://github.com/prisma/prisma/pull/28625). Thank you @bhbs! ### 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](https://pris.ly/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 ### ESM Prisma Client as the default The Rust-free/ESM Prisma Client has been in the works for some time now, all the way [back to v6.16.0](https://www.prisma.io/docs/orm/more/upgrade-guides/upgrading-versions/upgrading-to-prisma-6), 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 - Significantly simpler deployments Adopting the new client is as simple as swapping the `prisma-client-js` provider for `prisma-client` in your main `schema.prisma` : ```diff // schema.prisma generator client { - provider = "prisma-client-js" + provider = "prisma-client" } ``` ### Prisma Client changes In v7, we've moved to requiring users pass either an adapter or `accelerteUrl` when creating a new instance of `PrismaClient`. For Driver Adapters ```tsx import { PrismaClient } from './generated/prisma/client'; import { PrismaPg } from '@prisma/adapter-pg'; const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL }); const prisma = new PrismaClient({ adapter }); ``` For other databases: ```tsx // If using SQLite import { PrismaBetterSqlite3 } from '@prisma/adapter-better-sqlite3'; const adapter = new PrismaBetterSqlite3({ url: process.env.DATABASE_URL || 'file:./dev.db' }) // If using MySql import { PrismaMariaDb } from '@prisma/adapter-mariadb'; const adapter = new PrismaMariaDb({ host: "localhost", port: 3306, connectionLimit: 5 }); ``` We’ve also removed support for additional options when configuring your Prisma Client - `new PrismaClient({ datasources: .. })` support has been removed - `new PrismaClient({datasourceUrl: ..})` support has been removed - `new PrismaClient()` support has been removed - `new PrismaClient({})` support has been removed For Prisma Accelerate users: ```tsx import { PrismaClient } from "./generated/prisma/client" import { withAccelerate } from "@prisma/extension-accelerate" const prisma = new PrismaClient({ accelerateUrl: process.env.DATABASE_URL, }).$extends(withAccelerate()) ``` ### 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. ```groovy // 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: ```tsx // Import from the generated prisma client import { PrismaClient } from './generated/prisma/client'; ``` For developers who still need to stay on the `prisma-client-js` but are using the new `output` option, theres’s a new required package, `@prisma/client-runtime-utils` , which needs to be installed: ```bash # for prisma-client-js users only npm install @prisma/client-runtime-utils ``` ### Removal of implicit Prisma commands In previous releases, Prisma would run `generate` and `seed` in various situations: - post-install hook would run `prisma generate` - `prisma migrate` would run `prisma generate` and `prisma seed` This behaviour has been removed in favor of explicitly requiring commands to be run by users. ### Removal of `prisma generate` flags For `prisma generate` , we’ve removed a few flags that were no longer needed: - `prisma generate --data-proxy` - `prisma generate --accelerate` - `prisma generate --no-engine` - `prisma generate --allow-no-models` ### Removal of `prisma db` flags For `prisma db`, we’ve removed the following flag: - `prisma db pull --local-d1` This parameter no longer exists but equivalent functionality can be implemented by defining a config file with a connection string for the local D1 database. We provide a helper function listLocalDatabases in the D1 adapter to simplify the migration: ```ts import { defineConfig } from '@prisma/config' import { listLocalDatabases } from '@prisma/adapter-d1' export default defineConfig({ datasource: { url: `file://${listLocalDatabases().pop()}`, }, }) ``` ### Removal of `prisma migrate` flags For `prisma migrate diff`, we’ve removed the following flags: - `prisma --[from/to]-schema-datamodel` - This is now replaced with just `--[from/to]-schema`. The usage is otherwise the same. - `prisma --[from/to]-url`, `prisma --[from/to]-schema-datasource` - These are now replaced with `--[from/to]-config-datasource`. The user is expected to populate the datasource in the config file and use the new flag. We no longer support diffing two different URLs/datasources, since only one config can be used at a time. - `prisma --[from/to]-local-d1` - These are now replaced with `--[from/to]-config-datasource`. The user is expected to populate the datasource in the config file and use the new flag with a minor complication due to the fact that it needs to reference the local D1 database. Our `listLocalDatabases` helper function can be used for that, analogously to the `db pull --local-d1` example above (where the user sets the datasource URL to `file://${listLocalDatabases().pop()}`) ### MongoDB support in Prisma 7 Currently, MongoDB is not supported in Prisma 7. For folks using MongoDB, please stay on Prisma v6. We aim to add support for MongoDB in a future release. ### Driver Adapter naming updates We’ve standardized our naming conventions for the various driver adapters internally. The following driver adapters have been updated: - `PrismaBetterSQLite3` ⇒ `PrismaBetterSqlite3` - `PrismaD1HTTP` ⇒ `PrismaD1Http` - `PrismaLibSQL` ⇒ `PrismaLibSql` - `PrismaNeonHTTP` ⇒ `PrismaNeonHttp` ### Schema and config file updates As part of a larger change in how the Prisma CLI reads your project configuration, we’ve updated what get’s set the schema, and what gets set in the `prisma.config.ts` . Also as part of this release, `prisma.config.ts` is now required for projects looking to perform introspection and migration. **Schema changes** - `datasource.url` is now configured in the config file - `datasource.shadowDatabaseUrl` is now configured in the config file - `datasource.directUrl` has been made unnecessary and has removed - `generator.runtime=”react-native”` has been removed For early adopters of the config file, a few things have been removed with this release - `engine: 'js'| 'classic'` has been removed - `adapter` has been removed A brief before/after: ```groovy // schema.prisma datasource db { provider = "postgresql" url = ".." directUrl = ".." shadowDatabaseUrl = ".." } ``` ```tsx // ./prisma.config.ts export default defineConfig({ datasource: { url: '..', shadowDatabaseUrl: '..', } }) ``` ### Explicit loading of environment variables As part of the move to Prisma config, we’re no longer automatically loading environment variables when invoking the Prisma CLI. Instead, developers can utilize libraries like `dotenv` to manage their environment variables and load them as they need. This means you can have dedicated local environment variables or ones set only for production. This removes any accidental loading of environment variables while giving developers full control. ### Removed support for `prisma` keyword in `package.json` In previous releases, users could configure their schema entry point and seed script in a `prisma` block in the `package.json` of their project. With the move to `prisma.config.ts`, this no longer makes sense and has been removed. To migrate, use the Prisma config file instead: ```json { "name": "my-project", "version": "1.0.0", "prisma": { "schema": "./custom-path-to-schema/schema.prisma", "seed": "tsx ./prisma/seed.ts" } } ``` ```tsx import 'dotenv/config' import { defineConfig, env } from "prisma/config"; export default defineConfig({ schema: "prisma/schema.prisma", migrations: { seed: "tsx prisma/seed.ts" }, datasource: {...}, }); ``` ### Removed Client Engines: We’ve removed the following client engines: - `LibraryEngine` (`engineType = "library"`, the Node-API Client) - `BinaryEngine` (`engineType = "binary"`, the long-running executable binary) - `DataProxyEngine` and `AccelerateEngine` (Accelerate uses a new `RemoteExecutor` now) - `ReactNativeEngine` ### Deprecated metrics feature has been removed We deprecated the previewFeature `metrics` some time ago, and have removed it fully for version 7. If you need metrics related data available, you can use the underlying driver adapter itself, like the Pool metric from the Postgres driver. ### Miscellaneous - [#28493](https://github.com/prisma/prisma/pull/28493): Stop shimming `WeakRef` in Cloudflare Workers. This will now avoid any unexpected memory leaks. - [#28297](https://github.com/prisma/prisma/pull/28297): Remove hardcoded URL validation. Users are now required to make sure they don’t include sensitive information in their config files. - [#28273](https://github.com/prisma/prisma/pull/28273): Removed Prisma v1 detection - [#28343](https://github.com/prisma/prisma/pull/28343): Remove undocumented `--url` flag from `prisma db pull` - [#28286](https://github.com/prisma/prisma/pull/28286): Remove deprecated `prisma introspect` command. - [#28480](https://github.com/prisma/prisma/pull/28480): Rename `/wasm` to `/edge` - This change only affects `prisma-client-js` - Before: - `/edge` → meant “for Prisma Accelerate” - `/wasm` → meant “for Edge JS runtimes (e.g., Cloudflare, Vercel Edge)” - After: - `/edge` → means “for Edge JS runtimes (e.g., Cloudflare, Vercel Edge)” - The following Prisma-specific environment variables have been removed - `PRISMA_CLI_QUERY_ENGINE_TYPE` - `PRISMA_CLIENT_ENGINE_TYPE` - `PRISMA_QUERY_ENGINE_BINARY` - `PRISMA_QUERY_ENGINE_LIBRARY` - `PRISMA_GENERATE_SKIP_AUTOINSTALL` - `PRISMA_SKIP_POSTINSTALL_GENERATE` - `PRISMA_GENERATE_IN_POSTINSTALL` - `PRISMA_GENERATE_DATAPROXY` - `PRISMA_GENERATE_NO_ENGINE` - `PRISMA_CLIENT_NO_RETRY` - `PRISMA_MIGRATE_SKIP_GENERATE` - `PRISMA_MIGRATE_SKIP_SEED` ### Mapped enums If [you followed along on twitter](https://x.com/prisma/status/1988970132690071600), you will have seen that we teased a highly-request user feature was coming to v7.0. That highly-requested feature is…. mapped emuns! We now support the `@map` attribute for enum members, which can be used to set their expected runtime values ```groovy enum PaymentProvider { MixplatSMS @map("mixplat/sms") InternalToken @map("internal/token") Offline @map("offline") @@map("payment_provider") } ``` ```tsx export const PaymentProvider: { MixplatSMS: 'mixplat/sms' InternalToken: 'internal/token' Offline: 'offline' } ``` ## New Prisma Studio comes to the CLI We launched a new version of Prisma Studio to our Console and VS Code extension a while back, but the Prisma CLI still shipped with the older version. Now, with v7.0, we’ve updated the Prisma CLI to include the new Prisma Studio. Not only are you able to inspect your database, but you get rich visualization to help you understand connected relationships in your database. It’s customizable, much smaller, and can inspect remote database by passing a `--url` flag. This new version of Prisma Studio is not tied to the Prisma ORM, and establishes a new foundation for what comes next. Currently, the new studio only supports Postgres, MySQL, and SQLite, with support for other databases coming in a future release. For issues related to Prisma Studio, please direct them to the [Studio repo on github](https://github.com/prisma/studio). ![ScreenRecording2025-11-18at7 40 46PM-ezgif com-video-to-gif-converter](https://github.com/user-attachments/assets/0509b554-cbc6-48cc-adc5-ba491759895c) ## Prisma Postgres [Prisma Postgres](https://www.prisma.io/postgres) is our managed Postgres service, designed with the same philosophy of great DX that has guided Prisma for close to a decade. It works great with serverless, it’s fast, and with simple pricing and a generous free tier. Here’s what’s new: ### Connection Pooling Changes with Prisma Accelerate With support for connection pooling being added natively to Prisma Postgres, Prisma Accelerate now serves as a dedicated caching layer. If you were using Accelerate for the connection pooling features, don’t worry! Your existing connection string via Accelerate will continue to work, and you can switch to the new connection pool when you’re ready. ### Simplified connection flow We've made connecting to Prisma Postgres even simpler. Now, when you go to connect to a database, you’ll get new options to enable connection pooling, or to enable Prisma Accelerate for caching. Below, you’ll get code snippets for getting things configured in your project right away. ![Clipboard-20251119-110343-691](https://github.com/user-attachments/assets/172b43ee-70b3-43c7-a3ca-2cc12873d1a4) ### Serverless driver For those who want to connect to Prisma Postgres but are deploying to environments like Cloudflare Workers, we have a new version of the serverless client library to support these runtimes. - Compatible with Cloudflare Workers, Vercel Edge Functions, Deno Deploy, AWS Lambda, and Bun - Stream results row-by-row to handle large datasets with constant memory usage - Pipeline multiple queries over a single connection, reducing latency by up to 3x - SQL template literals with automatic parameterization and full TypeScript support - Built-in transactions, batch operations, and extensible type system [Check out the serverless driver docs](https://www.prisma.io/docs/postgres/database/serverless-driver) for more details ## Open roles at Prisma Interested in joining Prisma? We’re growing and have several exciting opportunities across the company for developers who are passionate about building with Prisma. Explore our open positions on our [Careers page](https://www.prisma.io/careers#current) and find the role that’s right for you. ## 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.9.0 Today, we are excited to share the `6.9.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.9.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/6.9.0) about the release.** ## Highlights ### Prisma ORM without Rust engines for PostgreSQL & SQLite (Preview) If you've been excited about our work of removing the Rust engines from Prisma ORM but hesitated trying it out because it was in an [Early Access](https://www.prisma.io/docs/orm/more/releases#early-access) (EA) phase, now is a great time for you to get your hands on the [Rust-free Prisma ORM version](https://www.prisma.io/blog/try-the-new-rust-free-version-of-prisma-orm-early-access). This major architectural change has moved from EA into [Preview](https://www.prisma.io/docs/orm/more/releases#preview) in this release, meaning there are no more know major issues. If you want to try it out, add the `queryCompiler` and `driverAdapters` preview feature flags to your `generator`, install the driver adapter for your database, and get going: ```prisma generator client { provider = "prisma-client-js" previewFeatures = ["queryCompiler", "driverAdapters"] output = "../generated/prisma" } ``` Now run `prisma generate` to re-generate Prisma Client. If you didn't use a [driver adapter](https://www.prisma.io/docs/orm/overview/databases/database-drivers#driver-adapters) before, you'll need to install, e.g. the one for PostgreSQL: ``` npm install @prisma/adapter-pg ``` Once installed, you can instantiate `PrismaClient` as follows: ```ts import { PrismaClient } from './generated/prisma' import { PrismaPg } from '@prisma/adapter-pg' const adapter = new PrismaPg({ connectionString: env.DATABASE_URL }) const prisma = new PrismaClient({ adapter }) ``` No more hassle with query engines, binary targets and an even smoother experience in serverless and edge environments! 📚 Learn more in the [docs](https://www.prisma.io/docs/orm/prisma-client/setup-and-configuration/no-rust-engine). ### Major improvements for local Prisma Postgres (Preview) In the last release, we enabled you to spin up a Prisma Postgres instance locally via the new `prisma dev` command. [Local Prisma Postgres](https://www.prisma.io/blog/prisma-6-8-0-release#local-development-for-prisma-postgres-early-access) uses PGlite under the hood and gives you an identical experience as you get with a remote Prisma Postgres instance. This release brings major improvements to this feature: - Persists your databases across `prisma dev` invocations. - Enables you to have multiple local Prisma Postgres instances running at the same time. - Running `prisma init` now uses local Prisma Postgres by default. Try it out and let us know what you think! 📚 Learn more in the [docs](https://www.prisma.io/docs/postgres/database/local-development). ## More news ### Connect to Prisma Postgres with any ORM (Preview) Since its [GA release](https://www.prisma.io/blog/prisma-postgres-the-future-of-serverless-databases), you could only interact with Prisma Postgres using Prisma ORM via a [custom connection string](https://www.prisma.io/docs/orm/reference/connection-urls#prisma-postgres). This has changed now: When setting up a new Prisma Postgres instance, you receive a regular PostgreSQL direct TCP connection string (starting with `postgres://...`) that lets you connect to it using your favorite tool or database library, including Drizzle, Kysely, TypeORM, and others. If you want to access Prisma Postgres from a serverless environment, you can also use our new [serverless driver](https://www.prisma.io/docs/postgres/database/serverless-driver) (Early Access). 📚 Learn more in the [docs](https://www.prisma.io/docs/postgres/database/direct-connections). ### Automated backup & restore Prisma Postgres' backup and restore mechanism has seen a major upgrade recently: You can now easily restore any previous backup via the UI in the Prisma Console. Find the new **Backups** tab when viewing your database and select any backup from the list to restore its state to a previous point in time. 📚 Learn more in the [docs](https://www.prisma.io/docs/postgres/database/backups). ### Prisma's VS Code extension now has a UI to manage Prisma Postgres If you're using Prisma ORM, chances are that you're using our [VS Code extension](https://marketplace.visualstudio.com/items?itemName=Prisma.prisma) too. In its latest release, we've added a major new capability to it: A UI for managing databases. With this new UI, you can: - Authenticate with the [Prisma Console](https://console.prisma.io) - Create and delete remote Prisma Postgres instances - View local Prisma Postgres instances - View and edit data via an embedded Prisma Studio - Visualize your database schema ![DB management in VS Code](https://cdn.sanity.io/images/p2zxqf70/production/f7a4f862f7f12d96c98eafef1b6bf0f2d0cac943-3740x1964.png) To use the new features, make sure to have the latest version of the Prisma VS Code extension installed and look out for the new **Prisma logo** in VS Code's _Activity Bar_. 📚 Learn more in the [docs](https://www.prisma.io/docs/postgres/integrations/vscode-extension#database-management-ui). ### New region for Prisma Postgres: San Francisco (`us-west-1`) We keep expanding Prisma Postgres availability across the globe! After having added Singapore just a few weeks ago, we're now adding San Francisco based on another [poll we ran on X](https://x.com/prisma/status/1924494260910612841). Here are all the regions where you can spin up Prisma Postgres instances today: - **`us-west-1`: San Francisco (_new!_)** - `us-east-1`: North Virginia - `eu-west-3`: Paris - `ap-northeast-1`: Tokyo - `ap-southeast-1`: Singapore [Keep an eye on our X account](https://pris.ly/x) to take part in the poll and vote for the next availability zone of Prisma Postgres! ### 6.8.2 Today, we are issuing the 6.8.2 patch release. It fully resolves an issue with the `prisma init` and `prisma dev` commands for some Windows users who were still facing problems after the previous incomplete fix in version 6.8.1. Fixes: * https://github.com/prisma/prisma/issues/27195 ### 6.8.1 Today, we are issuing the 6.8.1 patch release. It fixes an issue with the `prisma init` and `prisma dev` commands on Windows. Fixes - https://github.com/prisma/prisma/issues/27192 ### 6.8.0 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! ### 6.7.0 Today, we are excited to share the `6.7.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.7.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/6.7.0) about the release.** ## Highlights ### Prisma ORM without Rust engines (Early Access) If you're a regular visitor of our company blog, you may already know that we're currently working on moving the core of Prisma from Rust to TypeScript. We have written extensively about [why we're moving away from Rust](https://www.prisma.io/blog/from-rust-to-typescript-a-new-chapter-for-prisma-orm) and already shared [the first measurements of performance boosts](https://www.prisma.io/blog/rust-to-typescript-update-boosting-prisma-orm-performance) we saw from the re-write. This re-write is not just a move from one programming language to another. It fundamentally improves the architecture of Prisma ORM and replaces the Query Engine (which is written in Rust and deployed as a standalone binary) with a much leaner and more efficient approach that we call _Query Compiler_. In this release, we're excited to give you [Early Access](https://www.prisma.io/docs/orm/more/releases#early-access) to the new Query Compiler for PostgreSQL and SQLite database 🥳 Support for more database will follow very soon! To use the new "Rust-free" version of Prisma ORM, add the `queryCompiler` (_new_) and `driverAdapters` feature flags to your client generator: ```prisma generator client { provider = "prisma-client-js" previewFeatures = ["queryCompiler", "driverAdapters"] output = "../generated/prisma" } ``` Now run `prisma generate` to re-generate Prisma Client. If you didn't use a [driver adapter](https://www.prisma.io/docs/orm/overview/databases/database-drivers#driver-adapters) before, you'll need to install one. For example, the one for PostgreSQL: ``` npm install @prisma/adapter-pg ``` Once installed, you can instantiate `PrismaClient` as follows: ```ts import { PrismaPg } from '@prisma/adapter-pg' import { PrismaClient } from './generated/prisma' const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL }) const prisma = new PrismaClient({ adapter }) ``` This version of `PrismaClient` doesn't have a Query Engine binary and you can use it in the exact same way as before. 📚 Learn more in the [docs](https://www.prisma.io/docs/orm/prisma-client/setup-and-configuration/no-rust-engine). ### Support for `better-sqlite3` JavaScript driver (Preview) [Driver adapters](https://www.prisma.io/docs/orm/overview/databases/database-drivers) are Prisma ORM's way of letting you use JS-native drivers (like [`pg`](https://node-postgres.com/)) to interact with your database. In this release, we're introducing a new driver adapter for using the [`better-sqlite3`](https://github.com/WiseLibs/better-sqlite3) package, so you can now interact with SQLite database in a JS-native way. To use it, first enable the `driverAdapters` Preview feature flag in on your client `generator`, then install these libraries: ``` npm install @prisma/adapter-better-sqlite3 ``` Now you can instantiate Prisma Client as follows: ```ts import { PrismaBetterSQLite3 } from '@prisma/adapter-better-sqlite3'; import { PrismaClient } from './generated/prisma'; const adapter = new PrismaBetterSQLite3({ url: "file:./prisma/dev.db" }); const prisma = new PrismaClient({ adapter }); ``` 📚 Learn more in the [docs](https://www.prisma.io/docs/orm/overview/databases/sqlite#using-the-better-sqlite3-driver). ### Multi-file Prisma schemas are now production-ready The `prismaSchemaFolder` Preview feature is moving into General Availability 🎉 With that change, Prisma ORM now by default supports splitting your Prisma schema file and e.g. lets you organize your schema as follows: **`prisma/schema.prisma`** → defines data source and generator ```prisma datasource db { provider = "postgresql" url = env("DATABASE_URL") } generator client { provider = "prisma-client-js" } ``` **`prisma/models/posts.prisma`** → defines `Post` model ```prisma model Post { id Int @id @default(autoincrement()) title String content String? published Boolean @default(false) author User? @relation(fields: [authorId], references: [id]) authorId Int? } ``` **`prisma/models/users.prisma`** → defines `User` model ```prisma model User { id Int @id @default(autoincrement()) email String @unique name String? posts Post[] } ``` ⚠️ Note that there have been [breaking changes to the `prismaSchemaFolder` Preview feature in the last 6.6.0 release](https://github.com/prisma/prisma/releases/tag/6.6.0). If you've been using this feature to split your Prisma schema, make sure to read the release notes and update your project accordingly. 📚 Learn more in the [docs](https://www.prisma.io/docs/orm/prisma-schema/overview/location#multi-file-prisma-schema). ### Splitting generated output with new `prisma-client` generator (Preview) With the `prisma-client-js` generator, the generated Prisma Client library is put into a single `index.d.ts` file. This sometimes led to [issues](https://github.com/prisma/prisma/issues/4807) with large schemas where the size of the generated output could slow down code editors and breaking auto-complete. As of this release, our new `prisma-client` generator (that was released in [6.6.0](https://github.com/prisma/prisma/releases/tag/6.6.0)) now splits the generated Prisma Client library into multiple files and thus avoids the problems of a single, large output file. Also: As a bonus, we now ensure that generated files do not raise any ESLint and TypeScript errors! **Before** ``` generated/ └── prisma ├── client.ts ├── index.ts # -> this is split into multiple files in 6.7.0 └── libquery_engine-darwin.dylib.node ``` **After** ``` generated/ └── prisma ├── client.ts ├── commonInputTypes.ts ├── enums.ts ├── index.ts ├── internal │ ├── class.ts │ └── prismaNamespace.ts ├── libquery_engine-darwin.dylib.node ├── models │ ├── Post.ts │ └── User.ts └── models.ts ``` 📚 Learn more in the [docs](https://www.prisma.io/docs/orm/prisma-schema/overview/generators#output-splitting-and-importing-types). ## Company news Our team has been busy shipping more than just the ORM! Check out these articles to learn what else we've been up to recently: - [Announcing: Prisma Postgres Integration for Vercel Marketplace](https://www.prisma.io/blog/connect-your-apps-to-prisma-postgres-via-vercel-marketplace-integration) - [Securely Access Prisma Postgres from the Frontend (Early Access)](https://www.prisma.io/blog/securely-access-prisma-postgres-from-the-frontend-early-access) - [Announcing Prisma's MCP Server: Vibe Code with Prisma Postgres](https://www.prisma.io/blog/announcing-prisma-s-mcp-server-vibe-code-with-prisma-postgres) ### 6.6.0 Today, we are excited to share the `6.6.0` stable release 🎉 This version comes packed with exciting features, we can't wait to see what you're going to build with it! Read our announcement blog post for more details: [Prisma ORM 6.6.0: ESM Support, D1 Migrations & MCP Server](https://pris.ly/6.6.0-release?utm_source=github&utm_medium=6.6.0-release-notes) 🌟 **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.6.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/6.6.0) about the release.** 🌟 ## Highlights ### ESM support with more flexible `prisma-client` generator (Early Access) We are excited to introduce a new `prisma-client` generator that's more flexible, comes with ESM support and removes any magic behaviours that may cause friction with the current `prisma-client-js` generator. > **Note**: The `prisma-client` generator is currently in [Early Access](https://www.prisma.io/docs/orm/more/releases#early-access) and will likely have some breaking changes in the next releases. Here are the main differences: - Requires an `output` path; no “magic” generation into `node_modules` any more - Supports ESM and CommonJS via the `moduleFormat` field - Outputs plain TypeScript that's bundled just like the rest of your application code Here's how you can use the new `prisma-client` generator in your Prisma schema: ```prisma // prisma/schema.prisma generator client { provider = "prisma-client" // no `-js` at the end output = "../src/generated/prisma" // `output` is required moduleFormat = "esm" // or `"cjs"` for CommonJS } ``` In your application, you can then import the `PrismaClient` constructor (and anything else) from the generated folder: ```ts // src/index.ts import { PrismaClient } from './generated/prisma/client' ``` **⚠️ Important:** We recommend that you add the `output` path to `.gitignore` so that the query engine that's part of the generated Prisma Client is kept out of version control: ```bash # .gitignore ./src/generated/prisma ``` 📚 Learn more in the [docs](https://www.prisma.io/docs/orm/prisma-schema/overview/generators#prisma-client-early-acess). ### Cloudflare D1 & Turso/LibSQL migrations (Early Access) Cloudflare D1 and Turso are popular database providers that are both based on SQLite. While you can query them using the respective driver adapter for D1 or Turso, previous versions of Prisma ORM weren't able to make schema changes against these databases. With today's release, we're sharing the first [Early Access](https://www.prisma.io/docs/orm/more/releases#early-access) version of native D1 migration support for the following commands: - `prisma db push`: Updates the schema of the remote database based on your Prisma schema - `prisma db pull`: Introspects the schema of the remote database and updates your local Prisma schema - `prisma migrate diff`: Outputs the difference between the schema of the remote database and your local Prisma schema > **Note**: Support for `prisma migrate dev` and `prisma migrate deploy` will come very soon! To use these commands, you need to connect the Prisma CLI to your D1 or Turso instance by using the driver adapter in your [`prisma.config.ts`](https://www.prisma.io/docs/orm/reference/prisma-config-reference) file. Here is an example for D1: ```ts import path from 'node:path' import type { PrismaConfig } from 'prisma' import { PrismaD1HTTP } from '@prisma/adapter-d1' // import your .env file import 'dotenv/config' type Env = { CLOUDFLARE_D1_TOKEN: string CLOUDFLARE_ACCOUNT_ID: string CLOUDFLARE_DATABASE_ID: string } export default { earlyAccess: true, schema: path.join('prisma', 'schema.prisma'), migrate: { async adapter(env) { return new PrismaD1HTTP({ CLOUDFLARE_D1_TOKEN: env.CLOUDFLARE_D1_TOKEN, CLOUDFLARE_ACCOUNT_ID: env.CLOUDFLARE_ACCOUNT_ID, CLOUDFLARE_DATABASE_ID: env.CLOUDFLARE_DATABASE_ID, }) }, }, } satisfies PrismaConfig<Env> ``` With that setup, you can now execute schema changes against your D1 instance by running: ``` npx prisma db push ``` 📚 Learn more in the docs: - [Cloudflare D1](https://www.prisma.io/docs/orm/overview/databases/cloudflare-d1) - [Turso / LibSQL](https://www.prisma.io/docs/orm/overview/databases/turso) ### MCP server to manage Prisma Postgres via LLMs (Preview) [Prisma Postgres](https://www.prisma.io/postgres) is the first serverless database without cold starts. Designed for optimal efficiency and high performance, it's the perfect database to be used alongside AI tools like Cursor, Windsurf, Lovable or co.dev. In this ORM release, we're adding a command to start a Prisma MCP server that you can integrate in your AI development environment. Thanks to that MCP server, you can now: - tell your AI agent to create new DB instances - design your data model - chat through a database migration … and much more. To get started, add this snippet to the MCP configuration of your favorite AI tool and get started: ```json { "mcpServers": { "Prisma": { "command": "npx", "args": ["-y", "prisma", "mcp"] } } } ``` 📚 Learn more in the [docs](https://www.prisma.io/docs/postgres/mcp-server). ### New `--prompt` option on `prisma init` You can now pass a `--prompt` option to the `prisma init` command to have it scaffold a Prisma schema for you and deploy it to a fresh Prisma Postgres instance: ``` npx prisma init --prompt "Simple habit tracker application" ``` For everyone, following social media trends, we also created an alias called `--vibe` for you 😉 ``` npx prisma init --vibe "Cat meme generator" ``` ### Improved API for using driver adapters In this release, we are introducing a nice DX improvement for [driver adapters](https://www.prisma.io/docs/orm/overview/databases/database-drivers#driver-adapters). Driver adapters let you access your database using JS-native drivers with Prisma ORM. #### Before 6.6.0 Earlier versions of Prisma ORM required you to first instantiate the driver itself, and then use that instance to create the Prisma driver adapter. Here is an example using the `@libsql/client` driver for LibSQL: ```typescript import { createClient } from '@libsql/client' import { PrismaLibSQL } from '@prisma/adapter-libsql' import { PrismaClient } from '@prisma/client' // Old way of using driver adapters (before 6.6.0) const driver = createClient({ url: env.LIBSQL_DATABASE_URL, authToken: env.LIBSQL_DATABASE_TOKEN, }) const adapter = new PrismaLibSQL(driver) const prisma = new PrismaClient({ adapter }) ``` #### 6.6.0 and later As of this release, you instantiate the driver adapter _directly_ with the options of your preferred JS-native driver.: ```typescript import { PrismaLibSQL } from '@prisma/adapter-libsql' import { PrismaClient } from '../prisma/prisma-client' const adapter = new PrismaLibSQL({ url: env.LIBSQL_DATABASE_URL, authToken: env.LIBSQL_DATABASE_TOKEN, }) const prisma = new PrismaClient({ adapter }) ``` ## Other changes ### `prismaSchemaFolder` breaking changes If you are using the `prismaSchemaFolder` Preview feature to split your Prisma schema into multiple files, you may encounter some breaking changes in this version. #### Explicit declaration of schema folder location **You now _must_ always provide the path to the schema folder explicitly.** You can do this in either of three ways: - pass the the `--schema` option to your Prisma CLI command (e.g. `prisma migrate dev --schema ./prisma/schema`) - set the `prisma.schema` field in `package.json`: ```jsonc // package.json { "prisma": { "schema": "./schema" } } ``` - set the `schema` property in `prisma.config.ts`: ```ts import path from 'node:path' import type { PrismaConfig } from 'prisma' export default { earlyAccess: true, schema: path.join('prisma', 'schema'), } satisfies PrismaConfig<Env> ``` #### `migrations` folder must live next to `.prisma` file with `datasource` block Your `migrations` directory must live next to the `.prisma` file that defines your `datasource` blog. If you relied on the implicit schema folder location of `./prisma/schema` make sure to **move your migrations folder from `./prisma/migrations` to `./prisma/schema/migrations`**. Assuming `schema.prisma` defines the `datasource` in this example, here's how how need to place the `migrations` folder: ```bash # `migrations` and `schema.prisma` are on the same level . ├── migrations ├── models │ ├── posts.prisma │ └── users.prisma └── schema.prisma ``` See this [PR](https://github.com/prisma/prisma/pull/26663) for more details. ### No more Bun issues if Node.js is not installed Bun users reported an [issue](https://github.com/prisma/prisma/issues/26560) that `prisma generate` would hang if Node.js installed on their machine. This is now fixed and Bun users can generate Prisma Client without issues. ## Company news ### Enterprise support Prisma offers an [enterprise support plan](https://www.prisma.io/enterprise#contact-us) for Prisma ORM. Get direct help from our team and a joint slack channel! With [Prisma ORM 7](https://www.prisma.io/blog/rust-to-typescript-update-boosting-prisma-orm-performance) on the horizon, this is a great time to upgrade your support today. ### We are hiring: Developer Support Engineer If you care about making developers successful, [join us as a Developer Support Engineer](https://ats.rippling.com/en-GB/prisma-careers/jobs/cb7cea20-ada5-4cf8-8c91-174c7acd3047). ### 6.5.0 Today, we are excited to share the `6.5.0` stable release 🎉 🌟 **Help us spread the word about Prisma by starring the repo ☝️ or [tweeting](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v6.5.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/6.5.0) about the release.** 🌟 ## Highlights ### Databases can only be reset manually and explicitly In previous versions, if Prisma ORM determined that a `migrate` command could not be applied cleanly to the underlying database, you would get a message like this one: ``` ? We need to reset the "public" schema at "db.url.com:5432" Do you want to continue? All data will be lost. (y/N) ``` While "no" was the default, we've determined that having this prompt in the first place was a mistake. In this version we're removing the prompt entirely and instead exiting with an appropriate error message. To get the previous behavior, you will need to run `prisma migrate reset` directly. ### Support for `prisma.config.ts` in Prisma Studio We've expanded support for our `prisma.config.ts` file to include Prisma Studio! To use the new config file, including the ability to connect to driver adapter enabled databases with Prisma Studio, add a `studio` block to your `prisma.config.ts` file: ```ts import path from 'node:path' import type { PrismaConfig } from 'prisma' import { PrismaLibSQL } from '@prisma/adapter-libsql' import { createClient } from '@libsql/client' export default { earlyAccess: true, schema: { kind: 'single', filePath: './prisma/schema.prisma', }, studio: { adapter: async (env: unknown) => { const connectionString = `file:./dev.db' const libsql = createClient({ url: connectionString, }) return new PrismaLibSQL(libsql) }, }, } satisfies PrismaConfig ``` Notice how this looks a little different from last release! Instead of an `@prisma/config` package there’s now two different options: 1. Using the `defineConfig` helper exported by `prisma/config`. 2. Using the `PrismaConfig` utility type exported by `Prisma`. All the relevant info for the `prisma.config.ts` file, including these new ways of defining your config, [can be found in our docs](https://www.prisma.io/docs/orm/reference/prisma-config-reference). ### Allow for chaining `$on` and `$extends`. In previous versions of Prisma ORM, the return type of the `$on` client method was `void`. This did not allow for chaining `$on()` and `$extends()` calls, as `$on` is not available on extended clients. In this version we've resolved this issue and `$on` will now return the modified Prisma Client. ### Community fixes We have a number of community-submitted fixes that improve Prisma ORM: - [Allow for binaries to be loaded from local network](https://github.com/prisma/prisma/pull/23001). Thank you @RaHehl! - [Enhance type safety of the AtLeast utility type](https://github.com/prisma/prisma/pull/24056). Thank you @de-novo! - [Resolve a race condition in the NextJS monorepo plugin](https://github.com/prisma/prisma/pull/21370). Thank you @toniopelo! - [allow for filtering out spans with PrismaInstrumentation](https://github.com/prisma/prisma/pull/20113). Thank you @overbit! ## Prisma is hiring Join us at Prisma and work on [our TypeScript ORM (now faster than ever)](https://www.prisma.io/blog/rust-to-typescript-update-boosting-prisma-orm-performance) and our Cloud products [like Prisma Postgres (now in GA!)](https://www.prisma.io/blog/prisma-postgres-the-future-of-serverless-databases) We currently have two open roles in our Engineering team: - [Developer Support Engineer (Americas)](https://ats.rippling.com/prisma-careers/jobs/99a4a4e0-02ff-4e0a-867e-3730bcd9b6c3) - [Senior Engineering Manager](https://ats.rippling.com/prisma-careers/jobs/0f9295a1-6111-4814-bf9b-a5eb2002bf34) If these don’t fit, you can still check out our [jobs page](https://www.prisma.io/careers) and send a general application. ## Enterprise support Prisma offers an [enterprise support plan](https://www.prisma.io/enterprise#contact-us) for Prisma ORM. Get direct help from our team and a joint slack channel! [With Prisma ORM 7 on the horizon](https://www.prisma.io/blog/rust-to-typescript-update-boosting-prisma-orm-performance) this is a great time to upgrade your support today. ## Credits Thank you to @overbit, @RaHehl, @toniopelo, and @de-novo for your contributions to this release! --- ✨ This PR was created by Minori, your friendly dependency updater! 🌸

minori added 1 commit 2026-02-04 08:21:41 -08:00

deps: update prisma to 7.3.0

Node.js CI / CI (pull_request) Failing after 30s

Details

Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 1m29s

Details

d60eccd425

Node.js CI / CI (pull_request) Failing after 30s

Details

Security Scan and Upload / Security & DefectDojo Upload (pull_request) Successful in 1m29s

Details

This pull request doesn't have enough required approvals yet. 0 of 1 approvals granted from users or teams on the allowlist.

This branch is out-of-date with the base branch

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin dependencies/update-prisma:dependencies/update-prisma

git checkout dependencies/update-prisma

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: nhcarrigan/gwen-abalise#9

deps: update prisma to 7.3.0 #9

Dependency Update

Type

Changelog

Changelog

7.3.0

ORM

Open roles at Prisma

Enterprise support

7.2.0

Highlights

ORM

VS Code Extension

Open roles at Prisma

Enterprise support

7.1.0

Prisma ORM

Read Replicas extension

SQL comments

Basic usage

Query tags

Trace context

Custom plugins

Framework integration

Open roles at Prisma

Enterprise support

7.0.1

🛠 Fixes

7.0.0

Highlights

Prisma ORM

ESM Prisma Client as the default

Prisma Client changes

Generated Client and types move out of node_modules

Removal of implicit Prisma commands

Removal of prisma generate flags

Removal of prisma db flags

Removal of prisma migrate flags

MongoDB support in Prisma 7

Driver Adapter naming updates

Schema and config file updates

Explicit loading of environment variables

Removed support for prisma keyword in package.json

Removed Client Engines:

Deprecated metrics feature has been removed

Miscellaneous

Mapped enums

New Prisma Studio comes to the CLI

Prisma Postgres

Connection Pooling Changes with Prisma Accelerate

Simplified connection flow

Serverless driver

Open roles at Prisma

Enterprise support

6.9.0

Highlights

Prisma ORM without Rust engines for PostgreSQL & SQLite (Preview)

Major improvements for local Prisma Postgres (Preview)

More news

Connect to Prisma Postgres with any ORM (Preview)

Automated backup & restore

Prisma's VS Code extension now has a UI to manage Prisma Postgres

New region for Prisma Postgres: San Francisco (us-west-1)

6.8.2

6.8.1

6.8.0

Highlights

Local development with Prisma Postgres via prisma dev (Early Access)

Native Deno support in prisma-client generator (Preview)

VS Code Agent Mode: AI support with your database workflows

Other news

You voted, we acted: New Singapore region for Prisma Postgres

6.7.0

Highlights

Prisma ORM without Rust engines (Early Access)

Support for better-sqlite3 JavaScript driver (Preview)

Multi-file Prisma schemas are now production-ready

Splitting generated output with new prisma-client generator (Preview)

Company news

6.6.0

Generated Client and types move out of `node_modules`

Removal of `prisma generate` flags

Removal of `prisma db` flags

Removal of `prisma migrate` flags

Removed support for `prisma` keyword in `package.json`

New region for Prisma Postgres: San Francisco (`us-west-1`)

Local development with Prisma Postgres via `prisma dev` (Early Access)

Native Deno support in `prisma-client` generator (Preview)

Support for `better-sqlite3` JavaScript driver (Preview)

Splitting generated output with new `prisma-client` generator (Preview)

ESM support with more flexible `prisma-client` generator (Early Access)

New `--prompt` option on `prisma init`

`prismaSchemaFolder` breaking changes

`migrations` folder must live next to `.prisma` file with `datasource` block

Support for `prisma.config.ts` in Prisma Studio

Allow for chaining `$on` and `$extends`.