Packages

@opentelemetry/propagator-jaeger

2.12.0 · 6 Oct 2026Apache-2.030.9M / weekRepositoryHomepagenpmAtom feed

Deprecated by its maintainers: Package no longer supported. See https://github.com/open-telemetry/opentelemetry-js/pull/7077What to use instead
Your version

1.26.0

28 Aug 2024Where it was published

1.30.1 is the newest release of 1.x.

npm marks 1.26.0 as deprecated: Package no longer supported. See open-telemetry/opentelemetry-js#7077

In short

2 new3 fixed4 internal

Security

1 advisory affects 1.26.0; 2.9.0 fixes them

Release note

:rocket: (Enhancement)

  • Include instrumentation scope info in console span and log record exporters #4848

  • semconv: Update semantic conventions to 1.27 (from 1.7.0) #4690

    • Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.

    • Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.

    • Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.

:bug: (Bug Fix)

  • sdk-node: Avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879

  • instrumentation: Fix optional property types #4833

  • sdk-metrics: fix(sdk-metrics): use inclusive upper bounds in histogram #4829

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.