Skip to content

chore(deps): Bump @opentelemetry/api from 1.9.1 to 1.10.0 in the opentelemetry group across 1 directory - #653

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/opentelemetry-3d2892f4c7
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/opentelemetry-3d2892f4c7

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the opentelemetry group with 1 update in the / directory: @opentelemetry/api.

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)

🐛 (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)

🏠 (Internal)

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

@dependabot
dependabot Bot requested a review from h0mele55 as a code owner October 26, 2026 00:12
@dependabot @github

dependabot Bot commented on behalf of github Oct 26, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

Bumps the opentelemetry group with 1 update in the / directory: [@opentelemetry/api](https://github.com/open-telemetry/opentelemetry-js).


Updates `@opentelemetry/api` from 1.9.1 to 1.10.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-js/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-js/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-js@v1.9.1...v1.10.0)

---
updated-dependencies:
- dependency-name: "@opentelemetry/api"
  dependency-version: 1.10.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: opentelemetry
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title chore(deps): Bump @opentelemetry/api from 1.9.1 to 1.10.0 in the opentelemetry group chore(deps): Bump @opentelemetry/api from 1.9.1 to 1.10.0 in the opentelemetry group across 1 directory Nov 12, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/opentelemetry-3d2892f4c7 branch from 0998d30 to b3829a2 Compare November 12, 2026 12:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants