fix(deps): update opentelemetry-js monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@opentelemetry/api (source)	1.9.0 → 1.9.1
@opentelemetry/api-logs (source)	^0.54.0 → ^0.215.0
@opentelemetry/core (source)	2.2.0 → 2.7.0
@opentelemetry/exporter-logs-otlp-proto (source)	^0.54.0 → ^0.215.0
@opentelemetry/exporter-trace-otlp-proto (source)	^0.54.0 → ^0.215.0
@opentelemetry/otlp-exporter-base (source)	^0.208.0 → ^0.215.0
@opentelemetry/sdk-logs (source)	^0.54.0 → ^0.215.0
@opentelemetry/semantic-conventions (source)	1.38.0 → 1.40.0

---

Release Notes

open-telemetry/opentelemetry-js (@​opentelemetry/api)

v1.9.1

Compare Source

🐛 (Bug Fix)

• fix: avoid grpc types dependency #​3551 @​flarna
• fix(otlp-proto-exporter-base): Match Accept header with Content-Type in the proto exporter
  #​3562 @​scheler
• fix: include tracestate in export #​3569 @​flarna

🏠 (Internal)

• chore: fix cross project links and missing implicitly exported types #​3533 @​legendecas
• feat(sdk-metrics): add exponential histogram mapping functions #​3504 @​mwear

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 6am on the first day of the month"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: e6f7c44

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[devin-ai-integration]

Devin Review found 1 potential issue.

View 2 additional findings in Devin Review.

[devin-ai-integration]

🔴 Cross-generation OpenTelemetry version mismatch: 0.215.x exporters depend on sdk-trace-base@2.x but project uses sdk-trace-base@1.x

The PR bumps @opentelemetry/exporter-trace-otlp-proto from ^0.54.0 to ^0.215.0. Per the lockfile, this version transitively depends on @opentelemetry/sdk-trace-base@2.7.0 and @opentelemetry/resources@2.7.0. However, agents/package.json still declares @opentelemetry/sdk-trace-base: "^1.28.0" (resolves to 1.30.1) and @opentelemetry/sdk-trace-node: "^1.28.0" (resolves to 1.30.1).

In agents/src/telemetry/traces.ts:252-260, OTLPTraceExporter (0.215.0, built against sdk-trace-base@2.7.0) is passed to BatchSpanProcessor (from sdk-trace-node@1.30.1, built against sdk-trace-base@1.30.1). The exporter implements the SpanExporter interface from sdk-trace-base@2.x while the BatchSpanProcessor expects the SpanExporter interface from sdk-trace-base@1.x. This is an unsupported cross-generation configuration (experimental 0.215.x packages are designed for stable 2.x packages, not 1.x). The same applies to @opentelemetry/exporter-logs-otlp-proto@0.215.0 which depends on sdk-trace-base@2.7.0 and resources@2.7.0 internally. Before the PR, exporter-trace-otlp-proto@0.54.x used sdk-trace-base@1.27.x, which was correctly aligned with the 1.x generation.

Packages that should also be bumped to 2.x generation

• @opentelemetry/resources: ^1.28.0 → needs 2.x
• @opentelemetry/sdk-trace-base: ^1.28.0 → needs 2.x
• @opentelemetry/sdk-trace-node: ^1.28.0 → needs 2.x
• @opentelemetry/semantic-conventions: ^1.28.0 → may also need update

---

Was this helpful? React with 👍 or 👎 to provide feedback.