Impact Score: 5/10
Prisma 4.12.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.
โก Executive Summary (TL;DR)
Prisma 4.12.0. Source highlight: ๐ **Help us spread the word about Prisma by starring the repo or tweeting about the 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)
๐ **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%20v4.12.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/4.12.0) about the release.** ๐
## Highlights
### Introspection of Views SQL improvements (Preview)
The `views` Preview feature significantly improved this release: `prisma db pull` now reads the SQL query used to define a view and stores it in a `.sql` file in a `views` folder next to your Prisma schema.
> Note: These `.sql` files are not yet used for creating or updating views during migrations yet. For now, we are only looking for feedback. Let us know if the introspected SQL files match the views picked up in your database and if the correct files were created in your filesystem.
We encourage you to leave feedback in this [GitHub issue](https://github.com/prisma/prisma/issues/17335).
### Improvements to JSON protocol (Early Preview)
In [4.11.0](https://github.com/prisma/prisma/releases/tag/4.11.0), we announced the `jsonProtocol` Preview feature which had some rough edges. This release improves the Preview feature by providing polished and helpful error messages from Prisma Client when something goes wrong. Here is an example error message:

We would appreciate it if you would try it out to help us polish the feature and move it to General Availability. Testing it requires little effort. Please also leave any feedback in [this issue](https://github.com/prisma/prisma/issues/18095), or open a new one if you want to [report a bug](https://github.com/prisma/prisma/issues/new?assignees=&labels=kind/bug&template=bug_report.yml).
### Prisma Client startup performance
In this release, we've improved the startup performance of Prisma Client. We're keen on improving the performance of Prisma Client. If you experience any problems with the startup performance, be sure to [report them](https://github.com/prisma/prisma/issues/new?assignees=&labels=kind/bug&template=bug_report.yml) so that we can look into them.
### Open Telemetry tracing and logging for Prisma Client for Data Proxy
This release adds support for [Open Telemetry tracing](https://www.prisma.io/docs/concepts/components/prisma-client/opentelemetry-tracing) (via the `tracing` Preview feature) and [logging](https://www.prisma.io/docs/concepts/components/prisma-client/working-with-prismaclient/logging) to [Prisma Client for Data Proxy](https://www.prisma.io/docs/data-platform/data-proxy/use-data-proxy#generate-prisma-client-for-the-data-proxy).
## Fixes and improvements
### Prisma Migrate
- [Certain types of schema changes don't work with CockroachDB v22.2](https://github.com/prisma/prisma/issues/16909)
- [Completions: provided by engines break right at the start of a newline](https://github.com/prisma/prisma/issues/17000)
- [`db pull` fail with particular enum default value in column](https://github.com/prisma/prisma/issues/17047)
- [Unable to reset CockroachDB for table with foreign key relationship on v22.2.](https://github.com/prisma/prisma/issues/17055)
- [Introspection of SQLite views](https://github.com/prisma/prisma/issues/17416)
- [Changing the Column Type to Enum on a model throws an error](https://github.com/prisma/prisma/issues/17930)
- [Introspection of the view definition statement](https://github.com/prisma/prisma/issues/18366)
- [MySQL multi-value index removes the primary key on introspection](https://github.com/prisma/prisma/issues/18471)
### Prisma Client
- [`findUnique` used with `Promise.all` returns `null`](https://github.com/prisma/prisma/issues/18096)
- [Missing `PrismaPromise` export after update from 4.9.0 to 4.11.0](https://github.com/prisma/prisma/issues/18143)
- [jsonProtocol doesn't query enum fields by default](https://github.com/prisma/prisma/issues/18148)
- [Prisma 4.11 breaks multilevel relation with compound primary keys (typings)](https://github.com/prisma/prisma/issues/18173)
- [4.11.0: `Unique constraint failed on the fields` on query that worked in 4.10.1](https://github.com/prisma/prisma/issues/18186)
- [`jsonProtocol` Field/Enum is not included in the result of the findFirst/findMany function](https://github.com/prisma/prisma/issues/18200)
- [Too many records are returned in 4.11.0 when using nested include and @unique field is null](https://github.com/prisma/prisma/issues/18351)
- [Objects with computed properties returned from an extended prisma client return true for any property name when calling hasOwn or hasOwnProperty on it](https://github.com/prisma/prisma/issues/18462)
### Language tools (e.g. VS Code)
- [Completions: suggest `type` block for MongoDB](https://github.com/prisma/language-tools/issues/1368)
- [Remove datasource completions](https://github.com/prisma/language-tools/issues/1384)
## Credits
Huge thanks to @KhooHaoYit, @rintaun, @ivan, @art049 for helping!
## ๐บ Join us for another "What's new in Prisma" live stream
Learn about the latest release and other news from the Prisma community by joining us for another ["What's new in Prisma"](https://youtube.com/playlist?list=PLn2e1F9Rfr6l1B9RP0A9NdX7i7QIWfBa7) live stream.
The stream takes place [on YouTube](https://youtu.be/Ls4qDhRuyko) on **Thursday, March 30** at **5 pm Berlin | 8 am San Francisco**.