Bump @prisma/client from 5.12.1 to 5.22.0

[dependabot[bot]]

Bumps @prisma/client from 5.12.1 to 5.22.0.

Release notes

Sourced from @​prisma/client's releases.

5.22.0

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

• removing @unique in schema.prisma does not generate SQL to do so

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!

... (truncated)

Commits

• 718358a fix: integrate backwards compatibility change for Optimize (#25591)
• c64991b feat: integrate iTX and tracing refactor (#25285)
• b7210d9 chore: Small exports and changes for using Json Protocol types and utils in S...
• 9af950b chore(deps): update engines to 5.22.0-39.387bb643aa7d27f1f14d278b1a15691d8d4e...
• dd7d5ee chore: Expose serializeJsonQuery and deserializeJsonResponse (#25576)
• b599db6 chore(deps): update engines to 5.22.0-32.2428ad6eca74cb0654e6b55b8f19b662f2fa...
• 699552e chore: Expose JsonQuery type in @​prisma/client/runtime/library (#25557)
• 9567ac0 fix(adapter-d1): throws Error when string column contains any ISO date (#25483)
• 7496049 chore(deps): update engines to 5.22.0-12.8263a1f2b3deb0a72687cad83ceb981a2562...
• 8e14920 chore(deps): update engines to 5.22.0-10.4fe298bcdaa934021fad991610757e9d42ee...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)