Skip to content

Upgrade OpenTelemetry dependencies to support newer Sentry versions #2915

@argjent-doldadress

Description

@argjent-doldadress

Problem

@trigger.dev/core@4.3.2 is pinned to @opentelemetry/core@2.0.1, which is incompatible with @sentry/opentelemetry@10.12.0+.

Sentry changed their peer dependency requirement in version 10.12.0 from:
"@opentelemetry/core": "^1.30.1 || ^2.0.0"
to:
"@opentelemetry/core": "^1.30.1 || ^2.1.0"

This means anyone using both Trigger.dev and Sentry is stuck on @sentry/*@10.11.0, missing 6+ months of Sentry updates including security fixes, performance improvements, and new features like
continuous profiling.

Current Trigger.dev OpenTelemetry dependencies (4.3.2)

"@opentelemetry/core": "2.0.1"
"@opentelemetry/api-logs": "0.203.0"
"@opentelemetry/exporter-logs-otlp-http": "0.203.0"
"@opentelemetry/exporter-trace-otlp-http": "0.203.0"
"@opentelemetry/instrumentation": "0.203.0"
"@opentelemetry/resources": "2.0.1"
"@opentelemetry/sdk-logs": "0.203.0"
"@opentelemetry/sdk-trace-base": "2.0.1"
"@opentelemetry/sdk-trace-node": "2.0.1"

Requested upgrade

Please upgrade to at least:

  • @opentelemetry/core@^2.1.0
  • @opentelemetry/sdk-*@0.210.0 (or latest compatible)

Environment

  • Trigger.dev SDK version: 4.3.1 / 4.3.2
  • Node version: 22
  • Package manager: pnpm

Workaround

Currently the only workaround is downgrading Sentry to 10.11.0, which lacks newer features and fixes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions