Impact Score: 5/10
Prisma 4.6.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 4.6.1. Source highlight: Today, we are issuing the `4.6.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.
🔧 Bug Fixes & Patches (3)
- Prisma Client regression bug after upgrading to 4.6.0: `findMany` errors with `PANIC: index out of bounds: the len is 0 but the index is 0`
- `upsert()` with nested selection errors with `called `Option::unwrap()` on a `None` value` in 4.6.0
- Prisma 4.6.0 drops and recreates enum field when running db push even if the field has not changed
📄 View Raw Release Notes (Original Developer Log)
Today, we are issuing the `4.6.1` patch release.
## Fixes in Prisma Client
- [Prisma Client regression bug after upgrading to 4.6.0: `findMany` errors with `PANIC: index out of bounds: the len is 0 but the index is 0`](https://github.com/prisma/prisma/issues/16195)
- [`upsert()` with nested selection errors with `called `Option::unwrap()` on a `None` value` in 4.6.0](https://github.com/prisma/prisma/issues/16196)
## Fix in Prisma Migrate
- [Prisma 4.6.0 drops and recreates enum field when running db push even if the field has not changed](https://github.com/prisma/prisma/issues/16180)