Update opentelemetry-js monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@opentelemetry/api (source)	1.7.0 → 1.9.1
@opentelemetry/exporter-metrics-otlp-http (source)	^0.46.0 → ^0.222.0
@opentelemetry/exporter-trace-otlp-http (source)	^0.46.0 → ^0.222.0
@opentelemetry/resources (source)	1.19.0 → 1.30.1
@opentelemetry/sdk-trace-base (source)	1.19.0 → 1.30.1
@opentelemetry/sdk-trace-node (source)	1.19.0 → 1.30.1

---

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

v1.9.0

Compare Source

🚀 (Enhancement)

• feat(instrumentation-grpc): set net.peer.name and net.peer.port on client spans #​3430
• feat(exporter-trace-otlp-proto): Add protobuf otlp trace exporter support for browser #​3208 @​pkanal

🐛 (Bug Fix)

• fix(sdk-metrics): use default Resource to comply with semantic conventions #​3411 @​pichlermarc
  • Metrics exported by the SDK now contain the following resource attributes by default:
    • service.name
    • telemetry.sdk.name
    • telemetry.sdk.language
    • telemetry.sdk.version
• fix(sdk-metrics): use Date.now() for instrument recording timestamps #​3514 @​MisterSquishy
• fix(sdk-trace): make spans resilient to clock drift #​3434 @​dyladan
• fix(selenium-tests): updated webpack version for selenium test issue #​3456 @​SaumyaBhushan
• fix(sdk-metrics): collect metrics when periodic exporting metric reader flushes #​3517 @​legendecas
• fix(sdk-metrics): fix duplicated registration of metrics for collectors #​3488 @​legendecas
• fix(core): fix precision loss in numberToHrtime #​3480 @​legendecas

🏠 (Internal)

• chore: automatically generate tsconfigs #​3432 @​legendecas
• chore: enforce format with prettier #​3444 @​legendecas

v1.8.0

Compare Source

• @opentelemetry/sdk-metrics has been promoted to stable
• @opentelemetry/api-metrics has been merged into @opentelemetry/api and deprecated

💥 Breaking Change

• feat(api): merge api-metrics into api #​3374 @​legendecas

🚀 (Enhancement)

• feat(sdk-trace): re-export sdk-trace-base in sdk-trace-node and web #​3319 @​legendecas
• feat: enable tree shaking #​3329 @​pkanal

🐛 (Bug Fix)

• fix(sdk-trace): enforce consistent span durations
  #​3327 @​dyladan
• fix(resources): fix EnvDetector throwing errors when attribute values contain spaces
  #​3295
• fix(trace): fix an issue which caused negative span durations in web based spans
  #​3359 @​dyladan
• fix(resources): strict OTEL_RESOURCE_ATTRIBUTES baggage octet decoding
  #​3341 @​legendecas

📚 (Refine Doc)

• doc: Added Metrics documentation #​3360 @​weyert
• docs(api): fix counter negative value wording #​3396 @​legendecas

🏠 (Internal)

• ci: run browser tests without circle #​3328 @​dyladan

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @opentelemetry/core@1.19.0
npm error Found: @opentelemetry/api@1.9.1
npm error subgraphs/users/node_modules/@opentelemetry/api
npm error   @opentelemetry/api@"1.9.1" from ol-subgraph-users@0.0.0
npm error   subgraphs/users
npm error     ol-subgraph-users@0.0.0
npm error     node_modules/ol-subgraph-users
npm error       workspace subgraphs/users from the root project
npm error
npm error Could not resolve dependency:
npm error peer @opentelemetry/api@">=1.0.0 <1.8.0" from @opentelemetry/core@1.19.0
npm error subgraphs/users/node_modules/@opentelemetry/core
npm error   @opentelemetry/core@"1.19.0" from ol-subgraph-users@0.0.0
npm error   subgraphs/users
npm error     ol-subgraph-users@0.0.0
npm error     node_modules/ol-subgraph-users
npm error       workspace subgraphs/users from the root project
npm error
npm error Conflicting peer dependency: @opentelemetry/api@1.7.0
npm error node_modules/@opentelemetry/api
npm error   peer @opentelemetry/api@">=1.0.0 <1.8.0" from @opentelemetry/core@1.19.0
npm error   subgraphs/users/node_modules/@opentelemetry/core
npm error     @opentelemetry/core@"1.19.0" from ol-subgraph-users@0.0.0
npm error     subgraphs/users
npm error       ol-subgraph-users@0.0.0
npm error       node_modules/ol-subgraph-users
npm error         workspace subgraphs/users from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-16T03_34_06_950Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-16T03_34_06_950Z-debug-0.log