Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump @opentelemetry/sdk-metrics from 1.28.0 to 2.0.0 in /frontend #818

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 17, 2025

Bumps @opentelemetry/sdk-metrics from 1.28.0 to 2.0.0.

Release notes

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

v2.0.0

2.0.0

Summary

  • The minimum supported Node.js has been raised to ^18.19.0 || >=20.6.0. This means that support for Node.js 14 and 16 has been dropped.
  • The minimum supported TypeScript version has been raised to 5.0.4.
  • The compilation target for transpiled TypeScript has been raised to ES2022 (from ES2017).
  • The public interface has changed
  • Only experimental versions 0.200.0 are compatible with this release

💥 Breaking Change

  • feat(sdk-trace-base)!: Add parentSpanContext and remove parentSpanId from Span and ReadableSpan #5450 @​JacksonWeber
    • (user-facing): the SDK's Spans parentSpanId was replaced by parentSpanContext, to migrate to the new property, please replace span.parentSpanId -> span.parentSpanContext?.spanId
  • feat(sdk-metrics)!: drop deprecated type field on MetricDescriptor #5291 @​chancancode
  • feat(sdk-metrics)!: drop deprecated InstrumentDescriptor type; use MetricDescriptor instead #5277 @​chancancode
  • feat(sdk-metrics)!: bump minimum version of @opentelemetry/api peer dependency to 1.9.0 #5254 @​chancancode
  • chore(shim-opentracing): replace deprecated SpanAttributes #4430 @​JamieDanielson
  • chore(otel-core): replace deprecated SpanAttributes #4408 @​JamieDanielson
  • feat(sdk-metrics)!: remove MeterProvider.addMetricReader() in favor of constructor option #4419 @​pichlermarc
  • chore(otel-resources): replace deprecated SpanAttributes #4428 @​JamieDanielson
  • feat(sdk-metrics)!: remove MeterProvider.addMetricReader() in favor of constructor option #4419 @​pichlermarc
  • feat(sdk-metrics)!: replace attributeKeys with custom processors option #4532 @​pichlermarc
  • refactor(sdk-trace-base)!: replace SpanAttributes with Attributes #5009 @​david-luna
  • refactor(resources)!: replace ResourceAttributes with Attributes #5016 @​david-luna
  • feat(sdk-metrics)!: drop View and Aggregation in favor of ViewOptions and AggregationOption #4931 @​pichlermarc
  • refactor(sdk-trace-base)!: remove new Span constructor in favor of Tracer.startSpan API #5048 @​david-luna
  • refactor(sdk-trace-base)!: remove BasicTracerProvider.addSpanProcessor API in favor of constructor options. #5134 @​david-luna
  • refactor(sdk-trace-base)!: make resource property private in BasicTracerProvider and remove getActiveSpanProcessor API. #5192 @​david-luna
  • feat(sdk-metrics)!: extract IMetricReader interface and use it over abstract class #5311
    • (user-facing): MeterProviderOptions now provides the more general IMetricReader type over MetricReader
    • If you accept MetricReader in your public interface, consider accepting the more general IMetricReader instead to avoid unintentional breaking changes
  • feat(sdk-trace)!: remove ability to have BasicTracerProvider instantiate exporters #5239 @​pichlermarc
    • When extending BasicTracerProvider, the class offered multiple methods to facilitate the creation of exporters and auto-pairing with SpanProcessors.
      • This functionality has been removed - users may now pass SpanProcessors to the base class constructor when extending
      • (user-facing): _registeredExporters has been removed
      • (user-facing): _getSpanExporter has been removed
      • (user-facing): _buildExporterFromEnv has been removed
  • feat(core)!: remove deprecated IdGenerator and RandomIdGenerator #5309 @​pichlermarc
  • feat(core)!: remove deprecated type InstrumentationLibrary #5308 @​pichlermarc
    • (user-facing): please use equivalent type InstrumentationScope instead
  • feat(sdk-trace-base)!: replace usages fo InstrumentationLibrary with InstrumentationScope #5308 @​pichlermarc
    • (user-facing) rename Tracer.instrumentationLibrary -> Tracer.instrumentationScope
    • (user-facing) rename ReadableSpan.instrumentationLibrary -> ReadableSpan.instrumentationScope
      • also renames the property in implementations of ReadableSpan
  • feat(exporter-jaeger): use ReadableSpan.instrumentationScope over ReadableSpan.instrumentationLibrary #5308 @​pichlermarc
  • feat(exporter-zipkin): use ReadableSpan.instrumentationScope over ReadableSpan.instrumentationLibrary #5308 @​pichlermarc
  • chore!: update typescript to version 5.0.4 #5145 @​david-luna

... (truncated)

Changelog

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

2.0.0

Summary

  • The minimum supported Node.js has been raised to ^18.19.0 || >=20.6.0. This means that support for Node.js 14 and 16 has been dropped.
  • The minimum supported TypeScript version has been raised to 5.0.4.
  • The compilation target for transpiled TypeScript has been raised to ES2022 (from ES2017).
  • The public interface has changed
  • Only experimental versions 0.200.0 are compatible with this release

💥 Breaking Change

  • feat(sdk-trace-base)!: Add parentSpanContext and remove parentSpanId from Span and ReadableSpan #5450 @​JacksonWeber
    • (user-facing): the SDK's Spans parentSpanId was replaced by parentSpanContext, to migrate to the new property, please replace span.parentSpanId -> span.parentSpanContext?.spanId
  • feat(sdk-metrics)!: drop deprecated type field on MetricDescriptor #5291 @​chancancode
  • feat(sdk-metrics)!: drop deprecated InstrumentDescriptor type; use MetricDescriptor instead #5277 @​chancancode
  • feat(sdk-metrics)!: bump minimum version of @opentelemetry/api peer dependency to 1.9.0 #5254 @​chancancode
  • chore(shim-opentracing): replace deprecated SpanAttributes #4430 @​JamieDanielson
  • chore(otel-core): replace deprecated SpanAttributes #4408 @​JamieDanielson
  • feat(sdk-metrics)!: remove MeterProvider.addMetricReader() in favor of constructor option #4419 @​pichlermarc
  • chore(otel-resources): replace deprecated SpanAttributes #4428 @​JamieDanielson
  • feat(sdk-metrics)!: remove MeterProvider.addMetricReader() in favor of constructor option #4419 @​pichlermarc
  • feat(sdk-metrics)!: replace attributeKeys with custom processors option #4532 @​pichlermarc
  • refactor(sdk-trace-base)!: replace SpanAttributes with Attributes #5009 @​david-luna
  • refactor(resources)!: replace ResourceAttributes with Attributes #5016 @​david-luna
  • feat(sdk-metrics)!: drop View and Aggregation in favor of ViewOptions and AggregationOption #4931 @​pichlermarc
  • refactor(sdk-trace-base)!: remove new Span constructor in favor of Tracer.startSpan API #5048 @​david-luna
  • refactor(sdk-trace-base)!: remove BasicTracerProvider.addSpanProcessor API in favor of constructor options. #5134 @​david-luna
  • refactor(sdk-trace-base)!: make resource property private in BasicTracerProvider and remove getActiveSpanProcessor API. #5192 @​david-luna
  • feat(sdk-metrics)!: extract IMetricReader interface and use it over abstract class #5311
    • (user-facing): MeterProviderOptions now provides the more general IMetricReader type over MetricReader
    • If you accept MetricReader in your public interface, consider accepting the more general IMetricReader instead to avoid unintentional breaking changes
  • feat(sdk-trace)!: remove ability to have BasicTracerProvider instantiate exporters #5239 @​pichlermarc
    • When extending BasicTracerProvider, the class offered multiple methods to facilitate the creation of exporters and auto-pairing with SpanProcessors.
      • This functionality has been removed - users may now pass SpanProcessors to the base class constructor when extending
      • (user-facing): _registeredExporters has been removed
      • (user-facing): _getSpanExporter has been removed
      • (user-facing): _buildExporterFromEnv has been removed
  • feat(core)!: remove deprecated IdGenerator and RandomIdGenerator #5309 @​pichlermarc
  • feat(core)!: remove deprecated type InstrumentationLibrary #5308 @​pichlermarc
    • (user-facing): please use equivalent type InstrumentationScope instead
  • feat(sdk-trace-base)!: replace usages fo InstrumentationLibrary with InstrumentationScope #5308 @​pichlermarc
    • (user-facing) rename Tracer.instrumentationLibrary -> Tracer.instrumentationScope
    • (user-facing) rename ReadableSpan.instrumentationLibrary -> ReadableSpan.instrumentationScope
      • also renames the property in implementations of ReadableSpan
  • feat(exporter-jaeger): use ReadableSpan.instrumentationScope over ReadableSpan.instrumentationLibrary #5308 @​pichlermarc
  • feat(exporter-zipkin): use ReadableSpan.instrumentationScope over ReadableSpan.instrumentationLibrary #5308 @​pichlermarc
  • chore!: update typescript to version 5.0.4 #5145 @​david-luna
    • (user-facing) dropped support for typescript@<5.0.4

... (truncated)

Commits
  • 7fde940 chore: prepare release 2.0.0/0.200.0 (#5521)
  • ecd67de doc: add section to SDK 2.x migration guide for implementors of resource dete...
  • eaebf76 chore: prepare release 2.0.0-rc.1/0.200.0-rc.1 (#5534)
  • e947bd9 chore(deps): update dependency babel-loader to v10 (#5518)
  • 5e20647 fix(deps): update dependency axios to v1.8.2 [security] (#5532)
  • 78fc472 chore(deps): lock file maintenance (#5531)
  • 693b09d fix(core): avoid using util in configuration.ts for browser compatibility (#5...
  • 92fde6a chore: prepare 2.0.0-dev.1/0.200.0-dev.1 pre-release (#5512)
  • 04b3210 doc: upgrade/migration guide for SDK 2.0 (#5513)
  • cb48266 fix(deps): update dependency import-in-the-middle to v1.13.1 (#5517)
  • Additional commits viewable in compare view

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@opentelemetry/sdk-metrics](https://github.com/open-telemetry/opentelemetry-js) from 1.28.0 to 2.0.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.28.0...v2.0.0)

---
updated-dependencies:
- dependency-name: "@opentelemetry/sdk-metrics"
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Mar 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants