fix(deps): update prisma monorepo to v5.22.0
This MR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
@prisma/client (source) | dependencies | minor | 5.20.0 -> 5.22.0 |
prisma (source) | devDependencies | minor | 5.20.0 -> 5.22.0 |
Release Notes
prisma/prisma (@prisma/client)
v5.22.0
Today, we are excited to share the 5.22.0
stable 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
Prisma
- Prisma generate randomly fails on Ubuntu due to missing internal .so
libquery_engine-debian-openssl-1.1.x.so.node
- Timed out fetching a new connection from the connection pool.
- Some
prisma:engine:connection
spans have no parent - Query-related spans outside of
prisma:engine:itx_runner
are disconnected from the tree - Tracing with dataproxy/mini-proxy:
itx_runner
span and it's children are missing sometimes - Incorrect OpenTelemetry span reported by Prisma
- OTEL spans are not recognised as spans from a database
- SQL Injection bug - D1 adaptor throws "Conversion failed: expected a datetime string in column" when string column contains any ISO date
- Prisma generate randomly fails on Ubuntu due to missing internal .so
libquery_engine-debian-openssl-1.1.x.so.node
Credits
Huge thanks to @tmm1, @Takur0, @hinaloe, @andyjy, and @youxq for helping!
v5.21.1
- Fixed a bug where migrations were not using shadow database correctly in some edge cases
v5.21.0
Today, we are excited to share the 5.21.0
release
Highlights
Better support for tracing in MongoDB
The tracing
Preview feature now has full support for MongoDB with previously missing functionality now implemented. This is a part of the ongoing effort to stabilize this Preview feature and release it in General Availability.
tracing
is a Preview feature that enables built-in support for OpenTelemetry instrumentation inside the Prisma Client and provides deep insights into the performance and timing of your queries. See our documentation for more information.
For an easy to use and zero-configuration tracing instrumentation tool with a dashboard that provides an overview of your queries, statistics, and AI-powered recommendations, try Prisma Optimize.
WebAssembly engine size decrease for edge functions
Due to recent changes, some users experienced a steep increase of the bundle size in Prisma 5.20 when using the driverAdapters
Preview feature, going over the 1 MB limit on the free tier of Cloudflare Workers. This has now been fixed.
Fixes and improvements
Prisma Engines
Credits
Huge thanks to @austin-tildei, @LucianBuzzo, @mcuelenaere, @pagewang0, @key-moon, @pranayat, @yubrot, @skyzh for helping!
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.