Prisma 6.3.0stable Released Jan 28, 2025
Impact Score: 5/10

Prisma 6.3.0 — Release Notes & Engineering Impact

Source available — automated, not human-reviewed

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

Analysis updated: 2026-11-01.

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

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

Who Does This Impact? (Role-Based Analysis)

💻 Software Engineers & Devs

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

📊 Product & Engineering Leads

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

⚙️ DevOps & Security

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

✨ New Features & Capabilities (1)

  • Add `take` or `limit` to `updateMany()` & `deleteMany()`
📄 View Raw Release Notes (Original Developer Log)
Today, we are excited to share the `6.3.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.3.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/6.3.0) about the release.** 🌟 ## Highlights ### A brand new Prisma Studio In this release we've included several *great* improvements to Prisma Studio's developer experience. You can learn all about the changes we've made in our [release blog post](https://www.prisma.io/blog/we-made-prisma-studio-even-better), but here's a short list: #### Prisma Studio is back in the Console Fans of Prisma Data Browser rejoice! The new Prisma Studio is now in [the Prisma Console](https://console.prisma.io) and is available for all PostgreSQL and MySQL databases. #### A new model viewer Previously, switching from model to model in Prisma Studio would require backing all the way out to the model view, then digging in again. With our new UI, it's easy to switch from model to model while keeping your place. ![image](https://github.com/user-attachments/assets/beb3f4ed-7b7a-4f76-afd4-5b4a3081caff) #### A new editing experience If you're trying to edit a given field in a model, Prisma Studio made it quite easy. However, if you're trying to edit every field in a given row, it could get quite annoying to keep scrolling left to right. Our new edit sidebar resolves that with the ability to edit all fields for a given row at once. ![image](https://github.com/user-attachments/assets/00ca97d3-2fc6-4302-82c4-6290549be14a) #### Clean up at the click of a button When editing a number of models, it can get difficult to get back to a clean slate. In the new Prisma Studio, we've added a "Close all" button that puts you back to a fresh start. ![image](https://github.com/user-attachments/assets/847b0c5f-f67d-4cf1-986f-a178b965610b) ### Add `limit` to `updateMany()` and `deleteMany()` Previously, `limit` has not existed as a valid option in top level `updateMany()` and `deleteMany()` queries. In 6.3.0 `limit` is now available in these queries, bringing their features more in line with other query types. You can use `limit` like the following: ```tsx await prisma.user.deleteMany({ where: { column: 'value' }, limit: 100, }); ``` This will limit the number of deleted users to 100 at maximum. ### Sort `generator` fields deterministically In previous version of Prisma ORM, the fields inside of a `generator` block in your Prisma Schema were not deterministically sorted. This could lead to cases where `prisma db pull` could lead to re-ordering of fields. In 6.3.0, the sorting of fields in this block is now deterministic. You may see re-ordering on the first `prisma db pull` after you upgrade, but it will remain consistent afterwards. ### Replace `NOT IN` with `NOT EXISTS` for PostgreSQL relation filters In previous versions of Prisma ORM, when using the `none` or `some` relation filters, the SQL queries generated used `NOT IN`. In many cases this lead to performance issues as the size of the related table grew. In 6.3.0, we’ve replaced these usages of `IN` with `EXISTS` in order to improve query performance. ## A special thank you We'd like to extend our heartfelt thanks to @loren and his team for the collaboration and trust in our enterprise support plan. Working closely with them allowed us to address important issues like #19249 and #17303. Their insights and partnership have been invaluable in improving our product. If your team could benefit from dedicated support and tailored solutions, [learn more](https://www.prisma.io/enterprise?utm_source=release-notes&utm_campaign=thanks#contact-us) about our enterprise support plan. ## Fixes and improvements ### Prisma Client - [Add `take` or `limit` to `updateMany()` & `deleteMany()`](https://github.com/prisma/prisma/issues/6957) ### Prisma - [Prisma interactive transaction ignores DB exception on commit (with triggers)](https://github.com/prisma/prisma/issues/17303) - [`prisma db pull` non-deterministically sorts generator fields](https://github.com/prisma/prisma/issues/17899) - [`no entry found for key` error on views<->model relations](https://github.com/prisma/prisma/issues/19249) - [Adding `onUpdate` data to the DMMF in `@prisma/generator-helper`](https://github.com/prisma/prisma/issues/25944) ## Credits Huge thanks to @WhyAsh5114 for their contributions to this release!