Prisma 2.25.0stable Released Jun 15, 2021
⚠️ Breaking Change Impact Score: 7/10

Prisma 2.25.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.

Breaking-change evidence from the source

  • Breaking change ### Dropping support for Node.js v10
Read the original context ↗
Source flags breaking changes — review applicability
$ npm install --save-dev --save-exact [email protected]
📄 .MD
⚡ Executive Summary (TL;DR)

Prisma 2.25.0. Source highlight: Today, we are excited to share the `2.25.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.

⚠️ Breaking Changes & Deprecations (1)

  • Breaking change ### Dropping support for Node.js v10

✨ New Features & Capabilities (2)

  • Feature request - Migrate: When Drift Detected -> give more Details than just the rollback script
  • Prisma Studio not working with napi preview feature

⚡ Performance & Enhancements (2)

  • Possible Node API performance regression with concurrency
  • Performance regression with napi for high concurrency
📄 View Raw Release Notes (Original Developer Log)
Today, we are excited to share the `2.25.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%20v2.25.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/2.25.0) about the release.** 🌟  ## Major improvements & new features ### Human-readable drift diagnostics for `prisma migrate dev` Database schema drift occurs when your database schema is out of sync with your migration history, i.e. the database schema has _drifted away_ from the source of truth. With this release, we improve the way how the drift is printed to the console when detected in the `prisma migrate dev` command. While this is the only command that uses this notation in today's release, we plan to use it in other places where it would be useful for debugging in the future. Here is an example of how the drift is presented with the new format: ``` [*] Changed the `Color` enum [+] Added variant `TRANSPARENT` [-] Removed variant `RED` [*] Changed the `Cat` table [-] Removed column `color` [+] Added column `vaccinated` [*] Changed the `Dog` table [-] Dropped the primary key on columns (id) [-] Removed column `name` [+] Added column `weight` [*] Altered column `isGoodDog` (arity changed from Nullable to Required, default changed from `None` to `Some(Value(Boolean(true)))`) [+] Added unique index on columns (weight) ``` ### Support for `.env` files in Prisma Client Go You can now use a `.env` file with Prisma Client Go. This makes it easier to keep database credentials outside your Prisma schema and potentially work with multiple clients at the same time: ``` example/ ├── .env ├── main.go └── schema.prisma ``` Learn more about using the `.env` file in [our documentation](https://www.prisma.io/docs/concepts/more/environment-variables/#using-env-files). ## Breaking change ### Dropping support for Node.js v10 Node.js v10 reached End of Life on April 30th 2021. Many of our dependencies have already dropped support for Node.js v10 so staying up-to-date requires us to drop Node.js v10, too. We recommend upgrading to Node.js v14 or greater for long-term support. You can learn more about Node.js releases on [this page](https://nodejs.org/en/about/releases/). ## Fixes and improvements ### Prisma Client - [[Errors] New common error from malformed connection string](https://github.com/prisma/prisma/issues/3405) - [prisma client doesn't work with serverless-next.js](https://github.com/prisma/prisma/issues/6032) - [Failed to run future: no available capacity / QueueFull](https://github.com/prisma/prisma/issues/6683) - [Clean up middleware implementation](https://github.com/prisma/prisma/issues/6968) - [Possible Node API performance regression with concurrency](https://github.com/prisma/prisma/issues/7382) - [Dropping Node v10 support (LTS reached EndOfLife)](https://github.com/prisma/prisma/issues/7394) - [Performance regression with napi for high concurrency](https://github.com/prisma/prisma/issues/7404) - [In 2.24.0 `createMany` errors with: `PANIC in query-engine/connectors/sql-query-connector/src/database/operations/write.rs:95:60called `Result::unwrap()` on an `Err` value: ScalarFieldNotFound { name: "updated_at", model: "FundMangerTeamMemberExperience" }`](https://github.com/prisma/prisma/issues/7416) - [test: snapshot `params` in Middleware tests](https://github.com/prisma/prisma/issues/7437) - [Running `prisma generate` doesn't install prisma client 2.24.x](https://github.com/prisma/prisma/issues/7579) - [Middleware + $transactions do not play well together](https://github.com/prisma/prisma/issues/7584) - [Environment variable not found](https://github.com/prisma/prisma/issues/7629) ### Prisma Migrate - [Feature request - Migrate: When Drift Detected -> give more Details than just the rollback script](https://github.com/prisma/prisma/issues/5873) - [Error: [introspection-engine\connectors\sql-introspection-connector\src\introspection_helpers.rs:188:64] called `Option::unwrap()` on a `None` value ](https://github.com/prisma/prisma/issues/6738) - [Generate log file with Drift detected info for troubleshooting purpose](https://github.com/prisma/prisma/issues/6776) - [`db push` / `migrate` is hiding the binary download process during `generate`, leading to confusion](https://github.com/prisma/prisma/issues/6926) - [Shadow vs. main database check does not consider the port](https://github.com/prisma/prisma/issues/7216) - [Re-Introspection removes `shadowDatabaseUrl` from schema](https://github.com/prisma/prisma/issues/7337) ### Prisma Studio - [Prisma Studio not working with napi preview feature](https://github.com/prisma/studio/issues/662) - [Crash in simple datasource only schema](https://github.com/prisma/studio/issues/701) - [Prisma studio requires having prisma client installed when it shouldn't](https://github.com/prisma/studio/issues/703) ## Credits Huge thanks to @82600417, @SuryaElavazhagan, @psavan1655 for helping! ## 📺 Join us for another "What's new in Prisma" livestream Learn about the latest release and other news from the Prisma community by joining us for another ["What's new in Prisma"](https://www.youtube.com/watch?v=Fkj3Zaow5fQ&ab_channel=Prisma) livestream. The stream takes place [on Youtube](https://www.youtube.com/watch?v=Fkj3Zaow5fQ&ab_channel=Prisma) on **Thursday, June 17** at **5pm Berlin | 8am San Francisco**. ## 🌎 Prisma Day is coming Save the date for [Prisma Day 2021](https://www.prisma.io/day) and join us for two days of talks and workshops by the most exciting members of the Prisma community. - June 29th: Workshops - June 30th: Talks We look forward to seeing you there!