feat(node)!: Add support for Prisma v6 and drop v5 support

[AbhiPrasad]

ref #14793

In v9 of the SDK, we are dropping support for Prisma v5 in favour of Prisma v6.

Prisma v6 gives us much better traces, as well as the ability to enable prisma tracing without needing to update your prisma config.

This PR does not enable the Prisma integration by default, I will do that in a follow up PR where we can debate if we want to do it immediately for v9, or wait a little longer for it.

[spaceemotion]

Hi there! I just noticed that Sentry pulls in all the Prisma instrumentation by default - even if we don't use Prisma at all.

The README says that the package has to be installed if needed:

sentry-javascript/MIGRATION.md

Line 146 in f92f39b

1. Install the `@prisma/instrumentation` package with the desired version.

During build we are now getting duplicate package warnings about opentelemetry, since @prisma/instrumentation seems to be lagging behind.

Was adding the dependency directly supposed to be a peer dependency instead?

[lforst]

@spaceemotion super unsatisfying but: I don't think there's anything you can do except for ignoring the warnings. As it stands we're still gonna be depending on Prisma's instrumentation package going forward because we would like to have a 0 config experience. It may change int the mid-to-long-term future but that's where we're at.

[AbhiPrasad]

ref #14793

In v9 of the SDK, we are dropping support for Prisma v5 in favour of Prisma v6.

Prisma v6 gives us much better traces, as well as the ability to enable prisma tracing without needing to update your prisma config.

This PR does not enable the Prisma integration by default, I will do that in a follow up PR where we can debate if we want to do it immediately for v9, or wait a little longer for it.

[spaceemotion]

Hi there! I just noticed that Sentry pulls in all the Prisma instrumentation by default - even if we don't use Prisma at all.

The README says that the package has to be installed if needed:

sentry-javascript/MIGRATION.md

Line 146 in f92f39b

1. Install the `@prisma/instrumentation` package with the desired version.

During build we are now getting duplicate package warnings about opentelemetry, since @prisma/instrumentation seems to be lagging behind.

Was adding the dependency directly supposed to be a peer dependency instead?

[lforst]

@spaceemotion super unsatisfying but: I don't think there's anything you can do except for ignoring the warnings. As it stands we're still gonna be depending on Prisma's instrumentation package going forward because we would like to have a 0 config experience. It may change int the mid-to-long-term future but that's where we're at.

[AbhiPrasad]

ref #14793

In v9 of the SDK, we are dropping support for Prisma v5 in favour of Prisma v6.

Prisma v6 gives us much better traces, as well as the ability to enable prisma tracing without needing to update your prisma config.

This PR does not enable the Prisma integration by default, I will do that in a follow up PR where we can debate if we want to do it immediately for v9, or wait a little longer for it.

[spaceemotion]

Hi there! I just noticed that Sentry pulls in all the Prisma instrumentation by default - even if we don't use Prisma at all.

The README says that the package has to be installed if needed:

sentry-javascript/MIGRATION.md

Line 146 in f92f39b

1. Install the `@prisma/instrumentation` package with the desired version.

During build we are now getting duplicate package warnings about opentelemetry, since @prisma/instrumentation seems to be lagging behind.

Was adding the dependency directly supposed to be a peer dependency instead?

[lforst]

@spaceemotion super unsatisfying but: I don't think there's anything you can do except for ignoring the warnings. As it stands we're still gonna be depending on Prisma's instrumentation package going forward because we would like to have a 0 config experience. It may change int the mid-to-long-term future but that's where we're at.

[AbhiPrasad]

ref #14793

In v9 of the SDK, we are dropping support for Prisma v5 in favour of Prisma v6.

Prisma v6 gives us much better traces, as well as the ability to enable prisma tracing without needing to update your prisma config.

This PR does not enable the Prisma integration by default, I will do that in a follow up PR where we can debate if we want to do it immediately for v9, or wait a little longer for it.

[spaceemotion]

Hi there! I just noticed that Sentry pulls in all the Prisma instrumentation by default - even if we don't use Prisma at all.

The README says that the package has to be installed if needed:

sentry-javascript/MIGRATION.md

Line 146 in f92f39b

1. Install the `@prisma/instrumentation` package with the desired version.

During build we are now getting duplicate package warnings about opentelemetry, since @prisma/instrumentation seems to be lagging behind.

Was adding the dependency directly supposed to be a peer dependency instead?

[lforst]

@spaceemotion super unsatisfying but: I don't think there's anything you can do except for ignoring the warnings. As it stands we're still gonna be depending on Prisma's instrumentation package going forward because we would like to have a 0 config experience. It may change int the mid-to-long-term future but that's where we're at.

[AbhiPrasad]

ref #14793

In v9 of the SDK, we are dropping support for Prisma v5 in favour of Prisma v6.

Prisma v6 gives us much better traces, as well as the ability to enable prisma tracing without needing to update your prisma config.

This PR does not enable the Prisma integration by default, I will do that in a follow up PR where we can debate if we want to do it immediately for v9, or wait a little longer for it.

[spaceemotion]

Hi there! I just noticed that Sentry pulls in all the Prisma instrumentation by default - even if we don't use Prisma at all.

The README says that the package has to be installed if needed:

sentry-javascript/MIGRATION.md

Line 146 in f92f39b

1. Install the `@prisma/instrumentation` package with the desired version.

During build we are now getting duplicate package warnings about opentelemetry, since @prisma/instrumentation seems to be lagging behind.

Was adding the dependency directly supposed to be a peer dependency instead?

[lforst]

@spaceemotion super unsatisfying but: I don't think there's anything you can do except for ignoring the warnings. As it stands we're still gonna be depending on Prisma's instrumentation package going forward because we would like to have a 0 config experience. It may change int the mid-to-long-term future but that's where we're at.

[AbhiPrasad]

ref #14793

In v9 of the SDK, we are dropping support for Prisma v5 in favour of Prisma v6.

Prisma v6 gives us much better traces, as well as the ability to enable prisma tracing without needing to update your prisma config.

This PR does not enable the Prisma integration by default, I will do that in a follow up PR where we can debate if we want to do it immediately for v9, or wait a little longer for it.

[spaceemotion]

Hi there! I just noticed that Sentry pulls in all the Prisma instrumentation by default - even if we don't use Prisma at all.

The README says that the package has to be installed if needed:

sentry-javascript/MIGRATION.md

Line 146 in f92f39b

1. Install the `@prisma/instrumentation` package with the desired version.

During build we are now getting duplicate package warnings about opentelemetry, since @prisma/instrumentation seems to be lagging behind.

Was adding the dependency directly supposed to be a peer dependency instead?

[lforst]

@spaceemotion super unsatisfying but: I don't think there's anything you can do except for ignoring the warnings. As it stands we're still gonna be depending on Prisma's instrumentation package going forward because we would like to have a 0 config experience. It may change int the mid-to-long-term future but that's where we're at.

[AbhiPrasad]

ref #14793

In v9 of the SDK, we are dropping support for Prisma v5 in favour of Prisma v6.

Prisma v6 gives us much better traces, as well as the ability to enable prisma tracing without needing to update your prisma config.

This PR does not enable the Prisma integration by default, I will do that in a follow up PR where we can debate if we want to do it immediately for v9, or wait a little longer for it.

[spaceemotion]

Hi there! I just noticed that Sentry pulls in all the Prisma instrumentation by default - even if we don't use Prisma at all.

The README says that the package has to be installed if needed:

sentry-javascript/MIGRATION.md

Line 146 in f92f39b

1. Install the `@prisma/instrumentation` package with the desired version.

During build we are now getting duplicate package warnings about opentelemetry, since @prisma/instrumentation seems to be lagging behind.

Was adding the dependency directly supposed to be a peer dependency instead?

[lforst]

@spaceemotion super unsatisfying but: I don't think there's anything you can do except for ignoring the warnings. As it stands we're still gonna be depending on Prisma's instrumentation package going forward because we would like to have a 0 config experience. It may change int the mid-to-long-term future but that's where we're at.

[AbhiPrasad]

ref #14793

In v9 of the SDK, we are dropping support for Prisma v5 in favour of Prisma v6.

Prisma v6 gives us much better traces, as well as the ability to enable prisma tracing without needing to update your prisma config.

This PR does not enable the Prisma integration by default, I will do that in a follow up PR where we can debate if we want to do it immediately for v9, or wait a little longer for it.

[spaceemotion]

Hi there! I just noticed that Sentry pulls in all the Prisma instrumentation by default - even if we don't use Prisma at all.

The README says that the package has to be installed if needed:

sentry-javascript/MIGRATION.md

Line 146 in f92f39b

1. Install the `@prisma/instrumentation` package with the desired version.

During build we are now getting duplicate package warnings about opentelemetry, since @prisma/instrumentation seems to be lagging behind.

Was adding the dependency directly supposed to be a peer dependency instead?

[lforst]

@spaceemotion super unsatisfying but: I don't think there's anything you can do except for ignoring the warnings. As it stands we're still gonna be depending on Prisma's instrumentation package going forward because we would like to have a 0 config experience. It may change int the mid-to-long-term future but that's where we're at.