Skip to content

Bump Sentry OTEL @opentelemetry/* deps to >= 2.0.0 #16117

Closed as duplicate of#15737
@ian

Description

@ian

Problem Statement

Are there any published versions of @sentry/opentelemetry that support @opentelemetry/api >= 2.0.0?

This is holding back our upgrade of multiple @opentelemetry, langfuse, prisma, and vercel otel packages.

Solution Brainstorm

Here's what @sentry/otel locks at:

'@sentry/[email protected]':
resolution: {integrity: sha512-TLSP0n+sXKVcVkAM2ttVmXcAT2K3e9D5gdPfr6aCnW+KIGJuD7wzla/TIcTWFaVwUejbvXAB6IFpZ/qA8HFwyA==}
engines: {node: '>=18'}
peerDependencies:
'@opentelemetry/api': ^1.9.0
'@opentelemetry/context-async-hooks': ^1.30.1
'@opentelemetry/core': ^1.30.1
'@opentelemetry/instrumentation': ^0.57.1
'@opentelemetry/sdk-trace-base': ^1.30.1
'@opentelemetry/semantic-conventions': ^1.28.0

Bumping to ^2.0.0 would be helpful, I haven't yet looked to see what could potentially break.

If there's a canary release I'm happy to give it a try.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Waiting for: Product Owner

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions