Prisma 6.1.0 — Release Notes & Engineering Impact

Today we're releasing Prisma ORM version 6.1.0 In this version our `tracing` Preview feature is being graduated to GA! ## Highlights ### Tracing goes GA The `tracing` Preview feature is now stable. You now no longer have to include `tracing` in your set of enabled preview features. ```diff generator client { provider = "prisma-client-js" - previewFeatures = ["tracing"] } ``` We have also changed some of the spans generated by Prisma Client. Previously, a trace would report the following spans: ``` prisma:client:operation prisma:client:serialize prisma:engine prisma:engine:connection prisma:engine:db_query prisma:engine:serialize ``` Now, the following are reported: ``` prisma:client:operation prisma:client:serialize prisma:engine:query prisma:engine:connection prisma:engine:db_query prisma:engine:serialize prisma:engine:response_json_serialization ``` Additionally, we have made a few changes to our dependencies: - `@opentelemetry/api` is now a peer dependency instead of a regular dependency - `registerInstrumentations ` in `@opentelemetry/instrumentation` is now re-exported by `@prisma/instrumentation` After upgrading to Prisma ORM 6.1.0 you will need to add `@opentelemetry/api` to your dependencies if you haven't already: ``` npm install @opentelemetry/api ``` You will also no longer need to have `@opentelemetry/instrumentation` if you only use `registerInstrumentations`. In this case you can import `registerInstrumentations` from `@prisma/instrumentation` ```diff - import { PrismaInstrumentation } from '@prisma/instrumentation' + import { PrismaInstrumentation, registerInstrumentations } from '@prisma/instrumentation' ``` ### Mutli-line comments in Prisma Schema Language (PSL) Comments can now be defined as multi-line in your Prisma schema! Comments can use the existing format: ```prisma // this is a schema comment ``` or can now also use our multi-line format: ```prisma /* * this is a multi-line comment * You can add in all you want here * Keep typing and this comment will keep on going */ ``` ### Bug fixes #### Tracing related As we're moving our `tracing` preview to GA, a number of issues have been resolved. Here are a few highlights: - [Tests for tracing expanded and improved](https://github.com/prisma/prisma/issues/19224) - [Issues with Elastic APM addressed](https://github.com/prisma/prisma/issues/24715) - [Issues with Datadog tracer addressed](https://github.com/prisma/prisma/issues/22450) - [Prisma Client now respects `suppressTracing`](https://github.com/prisma/prisma/issues/17953) #### Other issues We also have a number of other issues that were resolved outside of our `tracing` feature. - [Resolved type issues with the `PrismaNeonHTTP` adapter](https://github.com/prisma/prisma/issues/25514) - [`findUnique` returns `null` when used instead of `Promise.all`](https://github.com/prisma/prisma/issues/25662) - [Resolved an issue with the latest version of Alpine Linux](https://github.com/prisma/prisma/issues/25817) ## Fixes and improvements ### Prisma - [Tracing: Detailed report and profiling informations](https://github.com/prisma/prisma/issues/1711) - [Prisma Client Request Tracing Integration](https://github.com/prisma/prisma/issues/5956) - [Instrumentation error in production: `TypeError: parentTracer.getSpanLimits is not a function`](https://github.com/prisma/prisma/issues/14887) - [Prisma is using the internal `Span` constructor](https://github.com/prisma/prisma/issues/16309) - [Prisma Client doesn't put all OTEL trace spans under one parent span](https://github.com/prisma/prisma/issues/16791) - [Prisma trace has unaccounted time](https://github.com/prisma/prisma/issues/17853) - [`prisma:engine` spans do not respect `suppressTracing()`](https://github.com/prisma/prisma/issues/17953) - [`tracing: engine` spans don't pass through `Sampler`](https://github.com/prisma/prisma/issues/19088) - [Add tests for tracing and different ways to open the first connection (including internal spans)](https://github.com/prisma/prisma/issues/19224) - [Tracing: Long trailing delay in `prisma:client:operation`](https://github.com/prisma/prisma/issues/19580) - [`prisma:engine` spans are missing when there are multiple `new PrismaClient()` invocations](https://github.com/prisma/prisma/issues/20779) - [`parentTracer.getSpanLimits is not a function`](https://github.com/prisma/prisma/issues/21397) - [Support tracers not derived from `opentelemetry-sdk-trace-base` (e.g. Datadog tracer)](https://github.com/prisma/prisma/issues/22450) - [`traceparent` comments with multiple SQL statements](https://github.com/prisma/prisma/issues/24370) - [Make `@prisma/instrumentation` dependencies peer dependencies](https://github.com/prisma/prisma/issues/24373) - [Make sure `db.statement` attribute doesn't include the `traceparent` comment](https://github.com/prisma/prisma/issues/24375) - [[Instrumentation] `registerInstrumentations` uses the global provider instead of the one passed in](https://github.com/prisma/prisma/issues/24488) - [Instrumentation: Problems in working with Elastic APM](https://github.com/prisma/prisma/issues/24715) - [`PrismaNeonHTTP` adapter breaks on some types e.g. timestamp](https://github.com/prisma/prisma/issues/25514) - [Promise.all() returns null with findUnique()](https://github.com/prisma/prisma/issues/25662) - [Alpine Linux 3.21: `Prisma failed to detect the libssl/openssl version to use`](https://github.com/prisma/prisma/issues/25817) ### Prisma Client - [Tracing operation duration bug under stress test](https://github.com/prisma/prisma/issues/16980) - [`@prisma/instrumentation` Type Error: `'InstrumentionNodeModuleDefintion' is not generic`](https://github.com/prisma/prisma/issues/24285)