Impact Score: 5/10
Prisma 2.4.1 — 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.
⚡ Executive Summary (TL;DR)
Prisma 2.4.1. Source highlight: Today, we are issuing the `2.4.1` patch 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.
📄 View Raw Release Notes (Original Developer Log)
Today, we are issuing the `2.4.1` patch release.
When we released the new "Order by multiple fields" feature, you gave us feedback, that the order of properties is not stable in JavaScript. Since ES2015 that is not a problem in the language itself anymore.
However, some teams use the [eslint sort-keys](https://eslint.org/docs/rules/sort-keys) plugin, which sorts the keys of objects by alphabet.
Therefore we decided to change the API in a patch release to minimize any problems this might cause to you.
## Order by multiple fields in `2.4.0`
```ts
// order by `age` descending and then by `name` ascending
const users = await prisma.user.findMany({
orderBy: {
age: 'desc',
name: 'asc'
}
})
```
## Order by multiple fields in `2.4.1`
```ts
// order by `age` descending and then by `name` ascending
const data = await client.user.findMany({
orderBy: [
{
age: 'desc',
},
{
name: 'asc',
},
],
})
```