Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 25, 2025

This PR contains the following updates:

Package Change Age Confidence
@prisma/client (source) 6.17.16.19.2 age confidence
prisma (source) 6.17.16.19.2 age confidence

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:

v6.19.1

Compare Source

v6.19.0

Compare Source

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 was generated by Mend Renovate. View the repository job log.

@vercel
Copy link

vercel bot commented Oct 25, 2025

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

Project Deployment Actions Updated (UTC)
callytics Ready Ready Preview, Comment Feb 2, 2026 10:04pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 25, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • 🔍 Trigger a full review

Comment @coderabbitai help to get the list of available commands and usage tips.

@socket-security
Copy link

socket-security bot commented Oct 25, 2025

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedprisma@​6.17.1 ⏵ 6.19.276 -181009798 +1100
Updated@​prisma/​client@​6.17.1 ⏵ 6.19.294 +110085 +198100

View full report

@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from 8b0a620 to b9c701e Compare October 30, 2025 22:04
@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from b9c701e to ed4ef44 Compare October 31, 2025 03:51
@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from ed4ef44 to 0eea023 Compare November 2, 2025 19:44
@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from 0eea023 to 0dc84b1 Compare November 5, 2025 14:56
@renovate renovate bot changed the title chore(deps): update prisma monorepo to v6.18.0 chore(deps): update prisma monorepo to v6.19.0 Nov 5, 2025
@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from 0dc84b1 to a8add89 Compare November 10, 2025 21:05
@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from a8add89 to f6d7925 Compare November 18, 2025 11:43
@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from f6d7925 to f2bafdf Compare December 3, 2025 18:03
@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from f2bafdf to 3d04cd3 Compare December 10, 2025 20:09
@renovate renovate bot changed the title chore(deps): update prisma monorepo to v6.19.0 chore(deps): update prisma monorepo to v6.19.1 Dec 10, 2025
@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from 3d04cd3 to 666778b Compare December 31, 2025 15:34
@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from 666778b to e78ec77 Compare January 13, 2026 14:39
@renovate renovate bot changed the title chore(deps): update prisma monorepo to v6.19.1 chore(deps): update prisma monorepo to v6.19.2 Jan 13, 2026
@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from e78ec77 to 22f2db6 Compare January 19, 2026 19:59
@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from 22f2db6 to 5ec400c Compare January 23, 2026 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants