@opentelemetry/core
3.1.1 · 9 Nov 2026Apache-2.0229.6M / weekRepositoryHomepagenpmAtom feed
Upgrading @opentelemetry/core From 2.12.1 to 3.1.1
3 releases in betweenevery note read
Reading releases, release notes and advisories…
- 16
- changes to make
- 0
- advisories fixed
- 2
- new
- 17
- fixes
Start here
Before you upgrade
Tick each one off as you go- Breaking3.1.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
- Fixed
resources: Specify full path for ioreg command on Darwin, and kenv command on BSD for
host.id@trentm
- Fixed
- Breaking
Raise the minimum
@opentelemetry/apipeer dependency version to 1.10.0 for packages that depend on@opentelemetry/core,@opentelemetry/otlp-transformeror@opentelemetry/instrumentation, as these use API 1.10 features. (#7258) @volodymyrshk @pichlermarc - Deprecated
resources: Deprecate
envDetectorin favor of separateresourceAttributesEnvDetectorandserviceNameEnvDetector. Also markserviceInstanceIdDetectoras stable (theservice.instance.idsemconv attribute is now stable). #6999 - New
sdk-logs, sdk-trace: Wait for each distinct pending resource once per batch instead of once per record #7208
- Fixed
context-zone: Declare the
@opentelemetry/apipeer dependency so Yarn PnP can resolve it forcontext-zone-peer-dep#7268 - Fixed
core: Accept attribute values with shared (non-circular) object references #7068
- Fixed
propagator-b3: Reject trace ids that are not 16 or 32 characters long #7262
- Breaking
- 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
18 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.