Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update prisma monorepo to v5.22.0 #1000

Merged
merged 1 commit into from
Jan 2, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 16, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@prisma/client (source) 5.21.1 -> 5.22.0 age adoption passing confidence
@prisma/instrumentation (source) 5.21.1 -> 5.22.0 age adoption passing confidence
prisma (source) 5.21.1 -> 5.22.0 age adoption passing confidence

Release Notes

prisma/prisma (@​prisma/client)

v5.22.0

Compare Source

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!


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner December 16, 2024 18:12
@renovate renovate bot requested review from bassrock and removed request for a team December 16, 2024 18:12
@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from 965788a to 8c117a6 Compare January 2, 2025 17:22
@renovate renovate bot force-pushed the renovate/prisma-monorepo branch from 8c117a6 to d3df3e6 Compare January 2, 2025 17:58
@bassrock bassrock merged commit dcd6aca into main Jan 2, 2025
210 checks passed
@bassrock bassrock deleted the renovate/prisma-monorepo branch January 2, 2025 18:11
Copy link

github-actions bot commented Jan 2, 2025

🎉 This PR is included in version @pocket-tools/tracing-v1.9.8 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant