[FEATURE]: Allow @opentelemetry/api@1.9.0

[maisano-patreon]

Package Name

dd-trace

Package Version(s)

No response

Describe the feature you'd like

Can we broaden the range of @opentelemetry/api to include 1.9.0? A transitive upgrade of this package recently resulted in a regression to the tracing of a project I work on (due to having 1.8.0 as the dd-trace transitive and 1.9.0 being a Sentry transitive).

The project in question is a Next.js app that makes use of TracerProvider.

Is your feature request related to a problem?

No response

Describe alternatives you've considered

I can pin to 1.8.0 but it would be ideal to use 1.9.0.

Additional context

Happy to submit a PR for this.

[maisano-patreon]

Opened #5503 assuming this change is kosher.

[GabDug]

👋 Hey! Small bump, as we're also impacted, as some backtage.io core plugins require 1.9.0.

We've reached out to Datadog support as well, hopefully this can help prioritize this issue :)

[public]

Support for Prisma tracing was recently added, but it currently requires work arounds to actually use by the looks of things due to this.

@prisma/instrumentation expects @opentelemetry/api@1.9.0 but dd-trace expects @opentelemetry/api@1.8.0

This results in Typescript not validating at the very least. This seems to be true all the way back to 6.1.0 which is the earliest version this is documented as working with which is a bit confusing.

[gabrielcolson]

@effect/opentelemtry is based on @opentelemtry/api@1.9.0 as well which requires us to override it on 1.8.0.

[meteorlxy]

bullmq-otel is also built with @opentelemtry/api@^1.9.0