Prisma 5.22.0 — Release Notes & Engineering Impact

Today, we are excited to share the `5.22.0` stable release 🎉 🌟 **Help us spread the word about Prisma by starring the repo ☝️ or [posting on X](https://twitter.com/intent/tweet?text=Check%20out%20the%20latest%20@prisma%20release%20v5.22.0%20%F0%9F%9A%80%0D%0A%0D%0Ahttps://github.com/prisma/prisma/releases/tag/5.22.0) about the release.** ## Highlights ### Further Tracing Improvements In our ongoing effort to stabilize the `tracing` Preview feature, we’ve made our spans compliant with OpenTelemetry Semantic Conventions for Database Client Calls. This should lead to better compatibility with tools such as DataDog and Sentry. We’ve also included numerous bug fixes that should make this Preview feature easier to work with. ### Metrics bug fix Occasionally, connection pool metrics would become negative or grow unbounded. In this release, connection pool metrics should stay consistent. ### Connection Pool Timeout fix In a specific case, there could be issues where fetching a new connection from the connection pool would time out, regardless of the state of the application and connection pool. If you have experience connection pool issues accessing a PostgreSQL database with TLS encryption in a resource-constrained environment (such as Function-as-a-Service offerings or very small VPS) this should resolve those issues. Special thanks to @youxq for their pull request and help resolving this issue! ## Join us Looking to make an impact on Prisma in a big way? We're hiring! Learn more on our careers page: https://www.prisma.io/careers ## Fixes and improvements ### Prisma Migrate - [removing `@unique` in `schema.prisma` does not generate SQL to do so](https://github.com/prisma/prisma/issues/12732) ### Prisma - [Prisma generate randomly fails on Ubuntu due to missing internal .so `libquery_engine-debian-openssl-1.1.x.so.node`](https://github.com/prisma/prisma/issues/19124) - [Timed out fetching a new connection from the connection pool. ](https://github.com/prisma/prisma/issues/25162) - [Some `prisma:engine:connection` spans have no parent](https://github.com/prisma/prisma/issues/23792) - [Query-related spans outside of `prisma:engine:itx_runner` are disconnected from the tree](https://github.com/prisma/prisma/issues/21402) - [Tracing with dataproxy/mini-proxy: `itx_runner` span and it's children are missing sometimes](https://github.com/prisma/prisma/issues/20694) - [Incorrect OpenTelemetry span reported by Prisma](https://github.com/prisma/prisma/issues/25436) - [OTEL spans are not recognised as spans from a database](https://github.com/prisma/prisma/issues/21472) - [SQL Injection bug - D1 adaptor throws "Conversion failed: expected a datetime string in column" when string column contains any ISO date](https://github.com/prisma/prisma/issues/25404) - [Prisma generate randomly fails on Ubuntu due to missing internal .so `libquery_engine-debian-openssl-1.1.x.so.node`](https://github.com/prisma/prisma/issues/19124) ## Credits Huge thanks to @tmm1, @Takur0, @hinaloe, @andyjy, and @youxq for helping!