Prisma: 5.22.0 Release

Release date:
November 5, 2024
Previous version:
5.21.1 (released October 17, 2024)
Magnitude:
980 Diff Delta
Contributors:
10 total committers
Data confidence:
Commits:

19 Commits in this Release

Ordered by the degree to which they evolved the repo in this version.

Authored November 4, 2024

Top Contributors in 5.22.0

aqrln
jkomyno
prisma-bot
SevInf
nikolasburk
justinvdm
Takur0
hinaloe
andyjy
tmm1

Directory Browser for 5.22.0

All files are compared to previous version, 5.21.1. Click here to browse diffs between other versions.

Loading File Browser...

Release Notes Published

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 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

Prisma

Credits

Huge thanks to @tmm1, @Takur0, @hinaloe, @andyjy, and @youxq for helping!