fix(deps): update prisma monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@prisma/adapter-better-sqlite3 (source)	7.0.0 -> 7.2.0
@prisma/adapter-better-sqlite3 (source)	6.19.0 -> 6.19.1
@prisma/adapter-d1 (source)	7.0.0 -> 7.2.0
@prisma/adapter-libsql (source)	7.0.0 -> 7.2.0
@prisma/adapter-pg (source)	7.0.0 -> 7.2.0
@prisma/adapter-pg (source)	6.20.0-integration-next.10 -> 6.20.0-integration-oidc-truster-publishers.2
@prisma/client (source)	7.0.0 -> 7.2.0
@prisma/client (source)	6.20.0-integration-next.10 -> 6.20.0-integration-oidc-truster-publishers.2
@prisma/client (source)	6.19.0 -> 6.19.1
@prisma/client (source)	6.9.0 -> 6.19.1
@prisma/client (source)	6.15.0 -> 6.19.1
prisma (source)	7.0.0 -> 7.2.0
prisma (source)	6.19.0 -> 6.19.1
prisma (source)	6.20.0-integration-next.10 -> 6.20.0-integration-oidc-truster-publishers.2
prisma (source)	6.9.0 -> 6.19.1
prisma (source)	6.15.0 -> 6.19.1

---

Release Notes

prisma/prisma (@​prisma/adapter-better-sqlite3)

v7.2.0

Compare Source

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.

v7.1.0

Compare Source

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.

v7.0.1

Compare Source

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 #​28583)
  • Fix collisions between user and internal Studio columns when querying (via #​28677)
  • Warn when SQLite file doesn't exist (via https://redirect.github.com/prisma/prisma/pull/28711/commits/c33a1ea9e5a94e6a5c876bc4567915cc5f354658)
  • Fix prisma/studio#1363 (via https://redirect.github.com/prisma/prisma/pull/28711/commits/07224d4651d043f4b08735eeaa144aa9d75f9fe3)
  • Sort tables alphabetically (via #​28702)

• Prisma CLI

  • Fix potential vulnerabilities in installed dependencies (via #​28592)
  • Fix #​28240, an exit code regression affecting prisma migrate diff (via prisma/prisma-engines#5699)
  • Show informative message when prisma db seed is run, but no migrations.seed command is specified in the Prisma config file (via #​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 #​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 #​28690)

• @​prisma/better-sqlite3

  • Bump underlying version of better-sqlite3 to ^12.4.5, fixing #​28624 (via #​28625). Thank you @​bhbs!

---

Configuration

📅 Schedule: Branch creation - "before 8am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.