Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
68 changes: 56 additions & 12 deletions pnpm-lock.yaml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

8 changes: 4 additions & 4 deletions pnpm-workspace.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -41,15 +41,15 @@ catalog:
'@nestjs/websockets': ^12.1.2
'@oazapfts/runtime': ^1.2.0
'@opentelemetry/api': ^1.9.0
'@opentelemetry/context-async-hooks': ^2.5.0
'@opentelemetry/core': ^2.5.0
'@opentelemetry/context-async-hooks': ^3.0.0
'@opentelemetry/core': ^3.0.0

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Keep the OpenTelemetry API and SDK generations compatible · compatibility

With the committed lockfile, @common/server resolves core, propagator-b3 and resources 3.1.1 against @opentelemetry/api 1.9.0, although all three now require >=1.10.0 <1.11.0. This introduces unsatisfied peer dependencies into the telemetry stack used by packages/common/src/otel/init.ts:2–10. Simply updating the API is not sufficient: sdk-node 0.217.0 and its SDK 2.x dependencies still require API <1.10.0. The upstream 3.x migration guide explicitly requires keeping API 1.9.x with SDK 2.x or migrating the SDK together.

Suggested fix

Restore the four catalog ranges to ^2.5.0 and regenerate pnpm-lock.yaml for now, or perform a coordinated SDK 3.x migration including API >=1.10.0 and the compatible SDK-node/exporter generation and initialization changes.

Prompt for a coding agent
In pnpm-workspace.yaml, restore @opentelemetry/context-async-hooks, @opentelemetry/core, @opentelemetry/propagator-b3 and @opentelemetry/resources to ^2.5.0, then regenerate pnpm-lock.yaml so they remain compatible with the existing API 1.9.0 and SDK-node 0.217.0. Do not upgrade API alone: the retained SDK 2.x packages require API <1.10.0. Defer the four major upgrades to a coordinated SDK 3.x migration.

'@opentelemetry/exporter-logs-otlp-proto': ^0.211.0
'@opentelemetry/exporter-metrics-otlp-proto': ^0.211.0
'@opentelemetry/exporter-trace-otlp-proto': ^0.211.0
'@opentelemetry/instrumentation-pino': ^0.57.0
'@opentelemetry/propagator-b3': ^2.5.0
'@opentelemetry/propagator-b3': ^3.0.0
'@opentelemetry/propagator-jaeger': ^2.5.0
'@opentelemetry/resources': ^2.5.0
'@opentelemetry/resources': ^3.0.0
'@opentelemetry/sdk-node': ^0.217.0
'@playwright/test': 1.63.0
'@sveltejs/adapter-auto': ^7.0.1
Expand Down
Loading