[dependabot]

Bumps the opentelemetry group with 3 updates in the / directory: @opentelemetry/api, @opentelemetry/sdk-trace-base and @opentelemetry/sdk-trace-node.

Updates @opentelemetry/api from 1.9.1 to 1.10.0

Release notes

Sourced from @​opentelemetry/api's releases.

api/v1.10.0

1.10.0

🚀 Features

• feat(api): integrate the Logs API into @opentelemetry/api #4862 @​hectorhdzg
• feat(api): add imperative context.attach() for setting context across callback boundaries that with() cannot wrap. #6845 @​pichlermarc
  • attach() returns a Token whose dispose() method restores the previous context. Use token.dispose() to detach.
  • attach is an optional method on the ContextManager interface; when the active context manager does not implement it, context.attach() logs a warning and returns a no-op token.
• feat(api): add AnyValue type (of type unknown) and extend Attributes type values to use AnyValue #6780 @​trentm
  • This is part of supporting OTEP 4485.
  • This is a breaking change for SDK implementations, in that they may need to support more attribute types for any APIs that accept Attributes or AnyValue. Implementors should refer to the OTEP 4485 link above for "MUST / SHOULD" requirements for complex attributes handling. See also the attributes-handling utilities provided by @opentelemetry/core to help. For example, cleanSimpleAttributes() can be used to limit user-provided attributes to the set of value types supported in earlier @opentelemetry/api versions.
  • This change is typically not a breaking change for users of @opentelemetry/api. There is one possible breaking case: If a TypeScript user was using the Attributes type in their own code and using TypeScript Narrowing to reduce an attribute value to an expected type (example here). It is expected that this usage should be rare and, likely, limited to SDK implementations, if at all. (If this impacted your code, please let us know.)
  • Note for users of attributes: Simple attributes SHOULD be used whenever possible. Instrumentations SHOULD assume that backends do not index individual properties of complex attributes, that querying or aggregating on such properties is inefficient and complicated, and that reporting complex attributes carries higher performance overhead.

🐛 Bug Fixes

• fix(api): cap tracestate list-members and total length in the deprecated TraceState.set() so it stays in step with TraceState from @opentelemetry/core #6964 @​Zuhef
• fix: resolve the ESM build through the default export condition instead of import, so a resolver that activates neither import nor require still finds an entry point #7132 @​overbalance

📚 Documentation

• docs(api): complete @since annotations for the public API #7023 @​nabeelamjadsheikh
  • Adds the three missing exported-type annotations and the member-level annotations for methods and properties introduced after their enclosing type.
  • Corrects Attributes, AttributeValue and TracerOptions from 1.3.0 to 1.1.0; all three were already importable in 1.1.0 via wildcard re-export.

🏠 Internal

• build: migrate the package build from tsc to tsdown, emitting dual CJS/ESM output from a single dist/ directory #6293 @​overbalance
  • The public entry points are unchanged: @opentelemetry/api and @opentelemetry/api/experimental. This package already declared an exports map, so deep imports such as @opentelemetry/api/build/src/... were rejected before this change and continue to be.
  • The emitted files moved out of build/src (CJS), build/esm and build/esnext (ESM) into dist/, using .cjs/.mjs extensions with matching .d.cts/.d.mts declarations. The non-standard esnext condition has been dropped in favour of the standard import/require conditions.
• perf(api): add getGlobal fast-path #6956 @​legendecas
• chore: remove the redundant module field from package.json; bundlers resolve the ESM build through the exports map #7130 @​overbalance

Changelog

Sourced from @​opentelemetry/api's changelog.

1.10.0

🚀 (Enhancement)

• feat(resource): create sync resource with some attributes that resolve asynchronously #3460 @​samimusallam
• feat: collect host id for non-cloud environments #3575 @​mwear
• feat (api-logs): separate Events API into its own package 3550 @​martinkuba
• feat(sdk-metrics): apply binary search in histogram recording #3539 @​legendecas
• perf(propagator-jaeger): improve deserializeSpanContext performance #3541 @​doochik
• feat: support TraceState in SamplingResult #3530 @​raphael-theriault-swi
• feat(sdk-trace-base): add diagnostic logging when spans are dropped #3610 @​neoeinstein
• feat: add unit to view instrument selection criteria #3647 @​jlabatut
• feat(tracing): expose dropped counts for attributes, events and links on span #3576 @​mohitk05

🐛 (Bug Fix)

• fix(core): added falsy check to make otel core work with browser where webpack config had process as false or null #3613 @​ravindra-dyte
• fix(instrumentation-http): include query params in http.target #3646 @​kobi-co

📚 (Refine Doc)

• chore: update http example #3651 @​JamieDanielson

🏠 (Internal)

• chore(exporter-jaeger): deprecate jaeger exporter #3585 @​pichlermarc
• fix(sdk-metrics): fix flaky LastValueAggregator test by using fake timer #3587 @​pichlermarc
• fix(test): fix failing tests by preventing source-map generation #3642 @​pichlermarc

Commits

• 56e6b1b chore: Release API 1.4.1, SDK 1.10.0, Experimental 0.36.0 (#3654)
• ecb5ebe fix: Minor typing issues for web sandbox (#3660)
• 48ecf22 feat(sdk-trace-base): add dropped attributes and events count on span (#3576)
• 95bf6fc fix(build): add example/http to ignore list in update-ts-configs (#3657)
• 3a2ca58 feat: add unit to view instrument selection criteria (#3647)
• ebc8575 chore(jeager-exporter): deprecate jaeger exporter (#3585)
• 2f715bd feat: allow to add attributes from grpc metadata in the patched server (#3589)
• cbbdfd3 fix(sdk-node): update instrumentations once MeterProvider is initialized (#3624)
• 4a4484a chore: update http example (#3651)
• 494efff fix(otlp-exporter-base): fix changelog for merged retry pr (#3650)
• Additional commits viewable in compare view

Updates @opentelemetry/sdk-trace-base from 2.10.0 to 2.12.0

Release notes

Sourced from @​opentelemetry/sdk-trace-base's releases.

v2.12.0

2.12.0

🚀 Features

• chore(sdk-trace): add StackContextManager in @opentelemetry/sdk-trace package #7086

🏠 Internal

• feat(ci): support releasing from maintenance branches #6767 @​pichlermarc
  • The API documentation site is only redeployed for releases whose commit is reachable from main, so a maintenance release no longer overwrites it.

v2.11.0

2.11.0

🚀 Features

• feat(context-async-hooks): implement attach() on AsyncLocalStorageContextManager #6845 @​pichlermarc
  • On Node.js 25.9+, delegates to AsyncLocalStorage.withScope() returning a native RunScope. On older Node.js, falls back to enterWith() with a manual disposable wrapper.
• feat(sdk-trace): allow configuring the force flush timeout per call #6929 @​LarryHu0217

🐛 Bug Fixes

• fix(sdk-metrics): ignore Infinity in exponential histograms #7015 @​mwear

🏠 Internal

• perf(sdk-metrics): reuse a single DataView for exponential histogram bit reads #6998 @​mwear
• chore(ci): run documentation tests on a weekly schedule #6920 @​LarryHu0217
• feat(ci): support pre-releases and major version bumps in the release workflow #6768 @​pichlermarc
• chore(resources): Ensure that multiple uses of serviceInstanceIdDetector.detect() return the same value for service.instance.id

Changelog

Sourced from @​opentelemetry/sdk-trace-base's changelog.

CHANGELOG

All notable changes to this project will be documented in this file.

For API changes, see the API CHANGELOG. For experimental package changes, see the experimental CHANGELOG. For semantic convention package changes, see the semconv CHANGELOG. For notes on migrating to 2.x / 0.200.x see the upgrade guide. For notes on migrating to 3.x see the 3.x migration guide.

Unreleased

💥 Breaking Changes

🚀 Features

🐛 Bug Fixes

📚 Documentation

🏠 Internal

• ci: update the W3C harness for Python 3.14 #7236 @​adityareddy-dev

3.0.0

💥 Breaking Changes

• chore(sdk-trace-node)!: remove the @opentelemetry/sdk-trace-node package #7054
  • The sdk-trace-node package has been replaced by the @opentelemetry/sdk-trace package. See the 3.x migration guide for full migration instructions.
• chore(shim-opentracing)!: remove the @opentelemetry/shim-opentracing package
  • In the OpenTelemetry Specification v1.56.0 the OpenTracing compatibility requirements were deprecated. The JavaScript OpenTracing shim package will not receive any more releases after the current 2.12.0 release (source code for last release).
• chore(context-async-hooks)!: remove the unused class AsyncHooksContextManager #7078
• feat!: 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 @​overbalance
  • Importing a package by its name is unaffected in both CommonJS and ESM, as is every subpath listed in its exports map.
  • Deep imports into the build output no longer resolve. An exports map is an allowlist that Node.js and bundlers enforce, so specifiers such as @opentelemetry/core/build/src/... or @opentelemetry/core/build/esm/... now fail with ERR_PACKAGE_PATH_NOT_EXPORTED. Rewriting them to the new file layout does not help — unlisted subpaths are rejected whether or not the file exists.
  • The emitted files moved out of build/src (CJS), build/esm and build/esnext (ESM) into dist/, using .cjs/.mjs extensions with matching .d.cts/.d.mts declarations.
  • <package>/package.json is no longer importable for the same reason. Read a package's version from your own dependency metadata, or use SDK_INFO from @opentelemetry/core for the SDK version.
  • The non-standard esnext entry point has been removed; tools that preferred it fall back to module (ESM) or main (CJS).
  • If you depend on something that is only reachable through a deep import, please open an issue so it can be considered for the public API.
• feat(core)!: remove deprecated getTimeOrigin, otperformance, _globalThis, and unrefTimer from @opentelemetry/core #7053
  • getTimeOrigin() — use performance.timeOrigin directly.
  • otperformance — use the global performance object directly.
  • _globalThis — use globalThis directly.
  • unrefTimer(timer) — call timer.unref() directly in your own code.
• feat(sdk-trace)!: remove deprecated TracerProviderOptions.forceFlushTimeoutMillis #7057
  • Pass timeoutMillis to provider.forceFlush({ timeoutMillis }) instead. The default timeout is 30000ms.
• feat(propagator-jaeger)!: remove @opentelemetry/propagator-jaeger package #7077

... (truncated)

Commits

• 92b844e chore: prepare next v2.x release (#7151)
• a859aff fix(web-common): export getElementXPath utility (#7124)
• 2bd5a73 chore(web-common)!: deprecate addSpanNetworkEvents() et al instrumentation-...
• d60f05e doc(sdk-trace): add description for StackContextManager (#7089)
• 5bd476e chore: move context manager to sdk-trace (#7086)
• 554c0c6 chore: move sdk-trace-web utils to web-common (#7058)
• 788922c ci: support maintenance branch releases (#7036)
• 0b72a81 chore: prepare next release (#7044)
• a9c5338 ci: roll prerelease changelog into one final release changelog (#7045)
• f41805e chore: prepare next release (#7042)
• Additional commits viewable in compare view

Updates @opentelemetry/sdk-trace-node from 2.10.0 to 2.12.0

Release notes

Sourced from @​opentelemetry/sdk-trace-node's releases.

v2.12.0

2.12.0

🚀 Features

• chore(sdk-trace): add StackContextManager in @opentelemetry/sdk-trace package #7086

🏠 Internal

• feat(ci): support releasing from maintenance branches #6767 @​pichlermarc
  • The API documentation site is only redeployed for releases whose commit is reachable from main, so a maintenance release no longer overwrites it.

v2.11.0

2.11.0

🚀 Features

• feat(context-async-hooks): implement attach() on AsyncLocalStorageContextManager #6845 @​pichlermarc
  • On Node.js 25.9+, delegates to AsyncLocalStorage.withScope() returning a native RunScope. On older Node.js, falls back to enterWith() with a manual disposable wrapper.
• feat(sdk-trace): allow configuring the force flush timeout per call #6929 @​LarryHu0217

🐛 Bug Fixes

• fix(sdk-metrics): ignore Infinity in exponential histograms #7015 @​mwear

🏠 Internal

• perf(sdk-metrics): reuse a single DataView for exponential histogram bit reads #6998 @​mwear
• chore(ci): run documentation tests on a weekly schedule #6920 @​LarryHu0217
• feat(ci): support pre-releases and major version bumps in the release workflow #6768 @​pichlermarc
• chore(resources): Ensure that multiple uses of serviceInstanceIdDetector.detect() return the same value for service.instance.id

Changelog

Sourced from @​opentelemetry/sdk-trace-node's changelog.

CHANGELOG

All notable changes to this project will be documented in this file.

For API changes, see the API CHANGELOG. For experimental package changes, see the experimental CHANGELOG. For semantic convention package changes, see the semconv CHANGELOG. For notes on migrating to 2.x / 0.200.x see the upgrade guide. For notes on migrating to 3.x see the 3.x migration guide.

Unreleased

💥 Breaking Changes

🚀 Features

🐛 Bug Fixes

📚 Documentation

🏠 Internal

• ci: update the W3C harness for Python 3.14 #7236 @​adityareddy-dev

3.0.0

💥 Breaking Changes

• chore(sdk-trace-node)!: remove the @opentelemetry/sdk-trace-node package #7054
  • The sdk-trace-node package has been replaced by the @opentelemetry/sdk-trace package. See the 3.x migration guide for full migration instructions.
• chore(shim-opentracing)!: remove the @opentelemetry/shim-opentracing package
  • In the OpenTelemetry Specification v1.56.0 the OpenTracing compatibility requirements were deprecated. The JavaScript OpenTracing shim package will not receive any more releases after the current 2.12.0 release (source code for last release).
• chore(context-async-hooks)!: remove the unused class AsyncHooksContextManager #7078
• feat!: 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 @​overbalance
  • Importing a package by its name is unaffected in both CommonJS and ESM, as is every subpath listed in its exports map.
  • Deep imports into the build output no longer resolve. An exports map is an allowlist that Node.js and bundlers enforce, so specifiers such as @opentelemetry/core/build/src/... or @opentelemetry/core/build/esm/... now fail with ERR_PACKAGE_PATH_NOT_EXPORTED. Rewriting them to the new file layout does not help — unlisted subpaths are rejected whether or not the file exists.
  • The emitted files moved out of build/src (CJS), build/esm and build/esnext (ESM) into dist/, using .cjs/.mjs extensions with matching .d.cts/.d.mts declarations.
  • <package>/package.json is no longer importable for the same reason. Read a package's version from your own dependency metadata, or use SDK_INFO from @opentelemetry/core for the SDK version.
  • The non-standard esnext entry point has been removed; tools that preferred it fall back to module (ESM) or main (CJS).
  • If you depend on something that is only reachable through a deep import, please open an issue so it can be considered for the public API.
• feat(core)!: remove deprecated getTimeOrigin, otperformance, _globalThis, and unrefTimer from @opentelemetry/core #7053
  • getTimeOrigin() — use performance.timeOrigin directly.
  • otperformance — use the global performance object directly.
  • _globalThis — use globalThis directly.
  • unrefTimer(timer) — call timer.unref() directly in your own code.
• feat(sdk-trace)!: remove deprecated TracerProviderOptions.forceFlushTimeoutMillis #7057
  • Pass timeoutMillis to provider.forceFlush({ timeoutMillis }) instead. The default timeout is 30000ms.
• feat(propagator-jaeger)!: remove @opentelemetry/propagator-jaeger package #7077

... (truncated)

Commits

• 92b844e chore: prepare next v2.x release (#7151)
• a859aff fix(web-common): export getElementXPath utility (#7124)
• 2bd5a73 chore(web-common)!: deprecate addSpanNetworkEvents() et al instrumentation-...
• d60f05e doc(sdk-trace): add description for StackContextManager (#7089)
• 5bd476e chore: move context manager to sdk-trace (#7086)
• 554c0c6 chore: move sdk-trace-web utils to web-common (#7058)
• 788922c ci: support maintenance branch releases (#7036)
• 0b72a81 chore: prepare next release (#7044)
• a9c5338 ci: roll prerelease changelog into one final release changelog (#7045)
• f41805e chore: prepare next release (#7042)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions