-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Support Prisma v6 #14793
Comments
Issue is triggered by: getsentry/sentry-javascript#14793
related: #14973 |
In terms of supporting both versions we have the following options.
Still debating through this, it's a little annoying that prisma instrumentation has such hard version constraints. I wish they separated it from the rest of prisma semvar. All 3 approaches should be easy, but 1 and 3 will require the most possible manual work from users. 2 is all automatic, but we keep the deps for a while. |
Updated our docs to make it clear that the SDK only supports |
Decision: For |
@AbhiPrasad, to clarify. |
@aried3r I haven't tested out I think we'll officially say that only |
Just leaving this here too because it was not obvious to me: Starting in v6 of Prisma, no client config is needed anymore, meaning tracing will work out of the box 🎉 |
Description
From: getsentry/sentry-docs#12184
https://github.com/prisma/prisma/releases/tag/6.1.0
On our side we've been evaluating merging in #14624 for v9 (considering it seems to be a breaking change in some ways).
We need to figure out:
6.x
bump for prisma instrumentation and still support5.x
? Ideally we can figure out how to support both at the same time so we support the max amount of users.5.x
and6.x
of the prisma integration work with8.x
and9.x
of the SDK.The text was updated successfully, but these errors were encountered: