@opentelemetry/core
3.1.1 · 9 Nov 2026Apache-2.0229.6M / weekRepositoryHomepagenpmAtom feed
Upgrading @opentelemetry/core From 2.12.1 to 3.0.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 14
- changes to make
- 0
- advisories fixed
- 1
- new
- 13
- fixes
Start here
Before you upgrade
Tick each one off as you go- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
- Breaking3.0.0
Release by release
- Breaking
sdk-trace-node: Remove the
@opentelemetry/sdk-trace-nodepackage #7054 - Breaking
shim-opentracing: Remove the
@opentelemetry/shim-opentracingpackage - Breaking
context-async-hooks: Remove the unused class
AsyncHooksContextManager#7078 - Breaking
Migrate package builds from
tsctotsdown, emitting dual CJS/ESM output from a singledist/directory and declaring anexportsmap on every package #6293
- Breaking
3 other lines we could not sort, mostly version bumps
- 3.0.0
The minimum supported Node.js has been raised to
>=22.15.0. This means that support for Node.js 18 and 20 has been dropped. - 3.0.0
The public interface has changed
- 3.0.0
Only experimental versions
0.300.0are compatible with this release
15 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.