fix(deps): update prisma monorepo to v6.19.2

[simonknittel]

This PR contains the following updates:

Package	Change	Age	Confidence
@prisma/client (source)	6.17.1 -> 6.19.2
@prisma/client (source)	6.6.0 -> 6.19.2
@prisma/instrumentation (source)	6.6.0 -> 6.19.2
prisma (source)	6.17.1 -> 6.19.2
prisma (source)	6.6.0 -> 6.19.2

---

Release Notes

prisma/prisma (@​prisma/client)

v6.19.2

Compare Source

Today, we are issuing a 6.19.2 patch release in the Prisma 6 release line. It fixes an issue with Prisma Accelerate support in some edge runtime configurations when the @prisma/client/edge entrypoint is not being used.

Changes:

• #​28934

v6.19.1

Compare Source

Today, we are issuing a patch release for Prisma 6 that includes a fix for a diffing bug introduced in Prisma 6.13.1, which led to incorrectly reported empty diffs.

Changes

• prisma/prisma-engines#5706

v6.19.0

Compare Source

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

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

Highlights

This release brings a lot of bug fixes and improvements to both the ORM and Prisma Postgres.

Prisma ORM

Prisma ORM is the most popular ORM in the TypeScript ecosystem. Today’s release brings a bunch of new bug fixes and overall improvements:

• #​5675: When dropping a model from a schema, do not append the default schema to the migration.
• #​5656: Align naming conventions for fields and relation fields
• #​28341: Add biome ignore comments to generated client files. This was a community contribution from @​lonelyevil, thank you!

Prisma Postgres

Prisma Postgres is our fully managed Postgres service, designed with the same philosophy of great DX that has guided Prisma for close to a decade. With this release, we are introducing the following improvements:

Connection pooling with Prisma Postgres

We added support for direct connections in 6.17, opening Prisma Postgres up to working with any tool in the wider Postgres ecosystem. Now, you can confirm that connection to support connection pooling by appending the query parameter pool=true to the connection string.

postgres://555555..../postgres?sslmode=require&pool=true

VS Code extension

A frequently requested feature is to be able to use a local Prisma Postgres database within our VS Code Extension without having to log in. In this release, we’re happy to share that this is now supported! Now you can work on your project without having to connect to the database remotely.

#​1924: previewFeatures = "" suggestion results in "[]" value

Preparing for Prisma v7

Prisma v7 is almost here, and we’ve been making many of the feature in it available ahead of its release. If you haven’t been keeping your version of prisma, @prisma/client up to date, now is the time to do so before the release. Many of the changes we’ve introduced over the 6.x release cycle will become the default in v7.

• Unified Prisma Config for project configuration
• Move from prisma-client-js prisma-client
• New engine and datasource keys in prisma.config.ts

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.

v6.18.0

Compare Source

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

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

Prisma ORM

Prisma ORM is the most popular ORM in the TypeScript ecosystem. Today’s release brings a bunch of new bug fixes and overall improvements:

• prisma init now creates a prisma.config.ts automatically

When creating a new project with 6.18.0, prisma init will now create a prisma.config.ts file automatically. This prepares new applications for the future of Prisma 7. Some fields that have been historically set in the schema.prisma file are now able to be set in the prisma.config.ts, and we encourage people to migrate over to the new structure before the release of version 7, where this file will become a requirement.

• Support for defining your datasource in prisma.config.ts

If you’re adopting the new prisma.config.ts setup in your projects, version 6.18.0 brings the ability to set your datasource directly in your config file. Once this is in your config file, any datasource set in your schema.prisma will be ignored. To set the datasource, we also must include the new engine key which we can set to "classic" , which will be required for Prisma v7

import { defineConfig, env } from "prisma/config";
export default defineConfig({
    // The Rust-compiled schema engine 
    engine: "classic",
    datasource: {
        url: env('DATABASE_URL'),
    }
});

• #​28291 Support multiple Prisma instances with different providers
• #​28305 Add env helper function
• #​28266 Add support for js or classic as engine types in prisma.config
• #​28139 Map Bytes to Uint8Array depending on Typescript version

Preparing for Prisma v7

While it has been mentioned a few times already, many of the changes in this release are here to prepare folks for the upcoming release of Prisma v7. It’s worth repeating that these changes and the migration to prisma.config.ts will be required for Prisma v7, so we’re releasing this as opt-in features for developers. But come Prisma v7, they will be the new way of configuring your project.

Prisma Postgres

Prisma Postgres is our fully managed Postgres service designed with the same philosophy of great DX that has guided Prisma for close to a decade. With this release we are introducing the following improvements:

Database Metric in Console

Inside of your database console, you can now view metrics on your database usage and interactions. You can get insights into the follow:

• Total egress
• Average response size
• Average query duration

In addition, you can also get insights into how to improve your query caching and gain better performance.

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.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

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

---

This PR has been generated by Renovate Bot.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Review	Updated (UTC)
sam	Ignored	Preview	Jan 27, 2026 6:15am

[Copilot]

Pull Request Overview

This PR updates the Prisma monorepo packages from versions 6.6.0/6.17.1 to 6.18.0, preparing the codebase for Prisma v7 by adopting the new prisma.config.ts configuration structure.

• Updates @prisma/client to version 6.18.0 across multiple packages
• Updates prisma CLI to version 6.18.0 in development dependencies
• Updates @prisma/instrumentation to version 6.18.0

Reviewed Changes

Copilot reviewed 2 out of 4 changed files in this pull request and generated 1 comment.

File	Description
pnpm-monorepo/packages/database/package.json	Updates @prisma/client and prisma to 6.18.0
app/package.json	Updates @prisma/client, @prisma/instrumentation, and prisma to 6.18.0

Files not reviewed (2)

• app/package-lock.json: Language not supported
• pnpm-monorepo/pnpm-lock.yaml: Language not supported

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The @prisma/adapter-pg package remains at version 6.17.1 while other Prisma packages are updated to 6.18.0. Consider updating this package to 6.18.0 to maintain consistency across the Prisma monorepo and avoid potential compatibility issues.

Suggested change

	"@prisma/adapter-pg": "6.17.1",
	"@prisma/adapter-pg": "6.18.0",

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	esbuild@​0.25.2 ⏵ 0.27.2			+1
	@​types/​web-push@​3.6.4
	lodash@​4.17.23
	prisma@​6.19.2
	@​types/​aws-lambda@​8.10.160
	web-push@​3.6.7
	prettier-plugin-organize-imports@​4.3.0
	@​prisma/​adapter-pg@​6.19.2
	@​prisma/​client@​6.6.0 ⏵ 6.19.2	+1		+2
	aws-xray-sdk-core@​3.12.0
	serialize-error@​12.0.0
	typescript@​5.9.3
	prettier@​3.8.0
	@​paralleldrive/​cuid2@​3.1.0
	@​prisma/​instrumentation@​6.6.0 ⏵ 6.19.2	+1
	zod@​3.25.76 ⏵ 4.3.5	+2
	@​aws-sdk/​client-ssm@​3.971.0
	@​aws-sdk/​client-dynamodb@​3.971.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm safer-buffer is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: pnpm-monorepo/pnpm-lock.yaml → npm/web-push@3.6.7 → npm/safer-buffer@2.1.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/safer-buffer@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud