@opentelemetry/core
3.1.1 · 9 Nov 2026Apache-2.0229.6M / weekRepositoryHomepagenpmAtom feed
Upgrading @opentelemetry/core From 1.17.0 to 1.30.1
18 releases in betweenevery note read
Reading releases, release notes and advisories…
- 2
- changes to make
- 0
- advisories fixed
- 19
- new
- 26
- fixes
Before you upgrade
Tick each one off as you go- Breaking1.18.0
- Deprecated1.26.0
Security
1 advisory still affects 1.30.1
- OpenTelemetry Core: Unbounded memory allocation in W3C Baggage propagationmoderate · GHSA-8988-4f7v-96qf
Upgrading to 2.8.0 clears it.
Release by release
- New
Add processors for adding session.id attribute to spans and logs #4972
- Fixed
sdk-trace-base: Avoid keeping non-string
status.messageonSpan#setStatus()#4999 - Fixed
sdk-metrics: Add missing catch and handle error in promise of
PeriodicExportingMetricReader#5006 - Fixed
opentelemetry-core: Confusing log extract of composite propagator #5017
- Fixed
propagator-aws-xray-*: Move propagators back to contrib repository #4966
- New
- Deprecated
Exported names from previous versions are deprecated.
- New
Include instrumentation scope info in console span and log record exporters #4848
- New
semconv: Update semantic conventions to 1.27 (from 1.7.0) #4690
- Fixed
sdk-node: Avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879
- Fixed
instrumentation: Fix optional property types #4833
- Fixed
sdk-metrics: fix(sdk-metrics): use inclusive upper bounds in histogram #4829
- Deprecated
1.25.1nothing new or fixed in the note
35 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.