Packages

@opentelemetry/core

3.1.1 · 9 Nov 2026Apache-2.0229.6M / weekRepositoryHomepagenpmAtom feed

Upgrading @opentelemetry/core From 2.12.0 to 3.1.1

4 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 2.12.0Newest 2.x2.12.1
  1. 2.12.0yours
  2. 2.12.1
  3. 3.0.0major
  4. 3.1.0breaking
  5. 3.1.1target
  6. 3 pre

Start here

Before you upgrade

Tick each one off as you go

Release by release

  1. 3.1.1

    9 Nov 20261 fix
    • Fixed

      resources: Specify full path for ioreg command on Darwin, and kenv command on BSD for host.id @trentm

  2. 3.1.0

    Migration needed5 Nov 20261 new · 3 fixes
    • Breaking

      Raise the minimum @opentelemetry/api peer dependency version to 1.10.0 for packages that depend on @opentelemetry/core, @opentelemetry/otlp-transformer or @opentelemetry/instrumentation, as these use API 1.10 features. (#7258) @volodymyrshk @pichlermarc

    • Deprecated

      resources: Deprecate envDetector in favor of separate resourceAttributesEnvDetector and serviceNameEnvDetector. Also mark serviceInstanceIdDetector as stable (the service.instance.id semconv 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/api peer dependency so Yarn PnP can resolve it for context-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

  3. 3.0.0

    Migration needed20 Oct 20261 new · 13 fixes
    • Breaking

      sdk-trace-node: Remove the @opentelemetry/sdk-trace-node package #7054

    • Breaking

      shim-opentracing: Remove the @opentelemetry/shim-opentracing package

    • Breaking

      context-async-hooks: Remove the unused class AsyncHooksContextManager #7078

    • Breaking

      Migrate package builds from tsc to tsdown, emitting dual CJS/ESM output from a single dist/ directory and declaring an exports map on every package #6293

  4. 2.12.1nothing new or fixed in the note

3 other lines we could not sort, mostly version bumps
  • 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.0 are compatible with this release

    3.0.0

19 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.