@opentelemetry/core
3.1.1 · 9 Nov 2026Apache-2.0229.6M / weekRepositoryHomepagenpmAtom feed
Upgrading @opentelemetry/core From 0.13.0 to 0.14.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 3
- changes to make
- 0
- advisories fixed
- 6
- new
- 4
- fixes
Before you upgrade
Tick each one off as you go- Breaking0.14.0
- Breaking0.14.0
- Breaking0.14.0
Security
1 advisory still affects 0.14.0
- OpenTelemetry Core: Unbounded memory allocation in W3C Baggage propagationmoderate · GHSA-8988-4f7v-96qf
Upgrading to 2.8.0 clears it.
Release by release
- Breaking
opentelemetry-api, opentelemetry-metrics: refactor: batch observer to be independent from metric types (@legendecas)
- Breaking
opentelemetry-api, opentelemetry-instrumentation-http, opentelemetry-instrumentation-xml-http-request, opentelemetry-plugin-fetch, opentelemetry-plugin-grpc-js, opentelemetry-plugin-grpc, opentelemetry-plugin-http, opentelemetry-shim-opentracing: chore: requires user to pass context to propagation APIs (@Flarna)
- Breaking
opentelemetry-api, opentelemetry-core, opentelemetry-grpc-utils, opentelemetry-node, opentelemetry-plugin-fetch, opentelemetry-plugin-grpc-js, opentelemetry-plugin-grpc, opentelemetry-plugin-http: chore: moving plugin from api to core (@obecny)
- New
opentelemetry-semantic-conventions: feat(semantic-conventions): messaging specifications (@nirsky)
- Breaking
1 internal line (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.