Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Apr 14, 2025

Bumps the opentelemetry group with 6 updates in the / directory:

Package From To
@opentelemetry/exporter-trace-otlp-grpc 0.57.2 0.200.0
@opentelemetry/instrumentation 0.57.2 0.200.0
@opentelemetry/resources 1.30.1 2.0.0
@opentelemetry/sdk-trace-base 1.30.1 2.0.0
@opentelemetry/sdk-trace-node 1.30.1 2.0.0
@opentelemetry/semantic-conventions 1.30.0 1.32.0

Updates @opentelemetry/exporter-trace-otlp-grpc from 0.57.2 to 0.200.0

Release notes

Sourced from @​opentelemetry/exporter-trace-otlp-grpc's releases.

experimental/v0.200.0

0.200.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 stable versions 2.0.0 are compatible with this release

💥 Breaking Change

  • feat(exporter-prometheus)!: stop the using type field to enforce naming conventions #5291 @​chancancode
    • Any non-monotonic sums will now be treated as counters and will therefore include the _total suffix.
  • feat(shim-opencenus)!: stop mapping removed Instrument type to OpenTelemetry metrics #5291 @​chancancode
    • The internal OpenTelemetry data model dropped the concept of instrument type on exported metrics, therefore mapping it is not necessary anymore.
  • feat(instrumentation-fetch)!: passthrough original response to applyCustomAttributes hook #5281 @​chancancode
    • Previously, the fetch instrumentation code unconditionally clones every fetch() response in order to preserve the ability for the applyCustomAttributes hook to consume the response body. This is fundamentally unsound, as it forces the browser to buffer and retain the response body until it is fully received and read, which crates unnecessary memory pressure on large or long-running response streams. In extreme cases, this is effectively a memory leak and can cause the browser tab to crash. If your use case for applyCustomAttributes requires access to the response body, please chime in on #5293.
  • chore!: Raise the minimum supported Node.js version to ^18.19.0 || >=20.6.0. Support for Node.js 14, 16, and early minor versions of 18 and 20 have been dropped. This applies to all packages except the 'api' and 'semantic-conventions' packages. #5395 @​trentm
  • feat(sdk-node)!: use IMetricReader over MetricReader #5311
    • (user-facing): NodeSDKConfiguration now provides the more general IMetricReader type over MetricReader
  • feat(exporter-metrics-otlp-http)!: do not read environment variables from window in browsers #5473 @​pichlermarc
    • (user-facing): all configuration previously possible via window.OTEL_* is now not supported anymore, please pass configuration options to constructors instead.
    • Note: Node.js environment variable configuration continues to work as-is.
  • feat(sdk-logs)!: do not read environment variables from window in browsers #5472 @​pichlermarc
    • (user-facing): all configuration previously possible via window.OTEL_* is now not supported anymore, please pass configuration options to constructors instead.
      • Note: Node.js environment variable configuration continues to work as-is.

🚀 (Enhancement)

  • feat(instrumentation-fetch): add a requestHook option #5380
  • feat(instrumentation): re-export initialize function from import-in-the-middle #5123
  • feat(sdk-node): lower diagnostic level #5360 @​cjihrig
  • feat(exporter-prometheus): add additional attributes option #5317 @​marius-a-mueller
    • Add withResourceConstantLabels option to ExporterConfig. It can be used to define a regex pattern to choose which resource attributes will be used as static labels on the metrics. The default is to not set any static labels.

🐛 (Bug Fix)

  • fix(instrumentation-grpc): monitor error events with events.errorMonitor #5369 @​cjihrig
  • fix(exporter-metrics-otlp-http): browser OTLPMetricExporter was not passing config to OTLPMetricExporterBase super class #5331 @​trentm
  • fix(instrumentation-fetch, instrumentation-xhr): Ignore network events with zero-timings #5332 @​chancancode
  • fix(exporter-logs/trace-otlp-grpc): fix error for missing dependency otlp-exporter-base #5412 @​JamieDanielson

🏠 (Internal)

  • chore(instrumentation-grpc): remove unused findIndex() function #5372 @​cjihrig
  • refactor(otlp-exporter-base): remove unnecessary isNaN() checks #5374 @​cjihrig
  • refactor(exporter-prometheus): remove unnecessary isNaN() check #5377 @​cjihrig

... (truncated)

Changelog

Sourced from @​opentelemetry/exporter-trace-otlp-grpc'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.

Unreleased

💥 Breaking Changes

🚀 Features

🐛 Bug Fixes

  • fix(resources): guard asynchronous resource attribute rejections from causing unhandled promise rejection #5544 @​dyladan
  • fix(resource): do not trigger Accessing resource attributes before async attributes settled warning when detecting resources #5546 @​dyladan
    • verbose logging of detected resource removed
  • fix(resource): use dynamic import over require to improve ESM compliance #5298 @​xiaoxiangmoe

📚 Documentation

🏠 Internal

  • test(sdk-metrics): fix multiple problematic assertRejects() calls #5611 @​cjihrig

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

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

Updates @opentelemetry/instrumentation from 0.57.2 to 0.200.0

Release notes

Sourced from @​opentelemetry/instrumentation's releases.

experimental/v0.200.0

0.200.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 stable versions 2.0.0 are compatible with this release

💥 Breaking Change

  • feat(exporter-prometheus)!: stop the using type field to enforce naming conventions #5291 @​chancancode
    • Any non-monotonic sums will now be treated as counters and will therefore include the _total suffix.
  • feat(shim-opencenus)!: stop mapping removed Instrument type to OpenTelemetry metrics #5291 @​chancancode
    • The internal OpenTelemetry data model dropped the concept of instrument type on exported metrics, therefore mapping it is not necessary anymore.
  • feat(instrumentation-fetch)!: passthrough original response to applyCustomAttributes hook #5281 @​chancancode
    • Previously, the fetch instrumentation code unconditionally clones every fetch() response in order to preserve the ability for the applyCustomAttributes hook to consume the response body. This is fundamentally unsound, as it forces the browser to buffer and retain the response body until it is fully received and read, which crates unnecessary memory pressure on large or long-running response streams. In extreme cases, this is effectively a memory leak and can cause the browser tab to crash. If your use case for applyCustomAttributes requires access to the response body, please chime in on #5293.
  • chore!: Raise the minimum supported Node.js version to ^18.19.0 || >=20.6.0. Support for Node.js 14, 16, and early minor versions of 18 and 20 have been dropped. This applies to all packages except the 'api' and 'semantic-conventions' packages. #5395 @​trentm
  • feat(sdk-node)!: use IMetricReader over MetricReader #5311
    • (user-facing): NodeSDKConfiguration now provides the more general IMetricReader type over MetricReader
  • feat(exporter-metrics-otlp-http)!: do not read environment variables from window in browsers #5473 @​pichlermarc
    • (user-facing): all configuration previously possible via window.OTEL_* is now not supported anymore, please pass configuration options to constructors instead.
    • Note: Node.js environment variable configuration continues to work as-is.
  • feat(sdk-logs)!: do not read environment variables from window in browsers #5472 @​pichlermarc
    • (user-facing): all configuration previously possible via window.OTEL_* is now not supported anymore, please pass configuration options to constructors instead.
      • Note: Node.js environment variable configuration continues to work as-is.

🚀 (Enhancement)

  • feat(instrumentation-fetch): add a requestHook option #5380
  • feat(instrumentation): re-export initialize function from import-in-the-middle #5123
  • feat(sdk-node): lower diagnostic level #5360 @​cjihrig
  • feat(exporter-prometheus): add additional attributes option #5317 @​marius-a-mueller
    • Add withResourceConstantLabels option to ExporterConfig. It can be used to define a regex pattern to choose which resource attributes will be used as static labels on the metrics. The default is to not set any static labels.

🐛 (Bug Fix)

  • fix(instrumentation-grpc): monitor error events with events.errorMonitor #5369 @​cjihrig
  • fix(exporter-metrics-otlp-http): browser OTLPMetricExporter was not passing config to OTLPMetricExporterBase super class #5331 @​trentm
  • fix(instrumentation-fetch, instrumentation-xhr): Ignore network events with zero-timings #5332 @​chancancode
  • fix(exporter-logs/trace-otlp-grpc): fix error for missing dependency otlp-exporter-base #5412 @​JamieDanielson

🏠 (Internal)

  • chore(instrumentation-grpc): remove unused findIndex() function #5372 @​cjihrig
  • refactor(otlp-exporter-base): remove unnecessary isNaN() checks #5374 @​cjihrig
  • refactor(exporter-prometheus): remove unnecessary isNaN() check #5377 @​cjihrig

... (truncated)

Changelog

Sourced from @​opentelemetry/instrumentation'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.

Unreleased

💥 Breaking Changes

🚀 Features

🐛 Bug Fixes

  • fix(resources): guard asynchronous resource attribute rejections from causing unhandled promise rejection #5544 @​dyladan
  • fix(resource): do not trigger Accessing resource attributes before async attributes settled warning when detecting resources #5546 @​dyladan
    • verbose logging of detected resource removed
  • fix(resource): use dynamic import over require to improve ESM compliance #5298 @​xiaoxiangmoe

📚 Documentation

🏠 Internal

  • test(sdk-metrics): fix multiple problematic assertRejects() calls #5611 @​cjihrig

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

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

Updates @opentelemetry/resources from 1.30.1 to 2.0.0

Release notes

Sourced from @​opentelemetry/resources'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/resources'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

Updates @opentelemetry/sdk-trace-base from 1.30.1 to 2.0.0

Release notes

Sourced from @​opentelemetry/sdk-trace-base'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-trace-base'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 <...

    Description has been truncated

    Note
    Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

    Summary by CodeRabbit

    • Chores
      • Upgraded observability/tracing dependencies used by Fastify plugins to newer releases. This improves trace export reliability, aligns with updated semantic conventions, and brings upstream fixes and performance improvements. No behavioral or configuration changes are required and peer dependency expectations remain unchanged; no action needed from users.

@dependabot dependabot bot requested review from a team, CarlosGamero, dariacm and kibertoad as code owners April 14, 2025 12:58
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch from 4e37db9 to 6ad9130 Compare April 21, 2025 12:33
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch 2 times, most recently from 53d4f11 to c4c4e22 Compare May 5, 2025 12:42
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch 3 times, most recently from 2a2fb8b to 8960aa5 Compare May 14, 2025 11:18
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch from 8960aa5 to ad11527 Compare May 19, 2025 12:49
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch 2 times, most recently from b350ccd to 1eb25b7 Compare June 2, 2025 12:58
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch from 1eb25b7 to 10088ea Compare June 9, 2025 13:08
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch from 10088ea to 4f24a4b Compare June 16, 2025 13:46
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch from 4f24a4b to 3621436 Compare June 23, 2025 14:10
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch 2 times, most recently from 4de98ad to d429d91 Compare July 7, 2025 15:20
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch 2 times, most recently from ba1c171 to 2c35e98 Compare July 21, 2025 13:06
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch from 2c35e98 to 10f55a8 Compare July 21, 2025 15:15
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch from 10f55a8 to d9de5b6 Compare July 28, 2025 18:20
@coderabbitai
Copy link

coderabbitai bot commented Jul 28, 2025

📝 Walkthrough

Walkthrough

Updated OpenTelemetry dependency versions in packages/app/context-fastify-plugins/package.json — several OpenTelemetry packages were bumped; no other files or code changes.

Changes

Cohort / File(s) Summary
OpenTelemetry dependency bumps
packages/app/context-fastify-plugins/package.json
Bumped dependency versions: @opentelemetry/exporter-trace-otlp-grpc and @opentelemetry/instrumentation0.205.0; @opentelemetry/resources, @opentelemetry/sdk-trace-base, @opentelemetry/sdk-trace-node2.1.0; @opentelemetry/semantic-conventions1.37.0. No other edits.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Pre-merge checks

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The pull request description does not follow the required template structure. While the description provides extensive information about the OpenTelemetry dependency updates through a version table and detailed release notes, it is missing the required "Changes" section and the "Checklist" section specified in the template. The checklist items—including the mandatory label selection (major/minor/patch/skip-release), documentation update status, and test update status—are not present in the description as checkboxes or explicit statements, despite being required by the template. Although the PR objectives mention that "major, skip-release" labels were applied, these are not documented in the pull request description itself. The pull request description should be updated to match the required template format. Add a "## Changes" section that provides a clear summary of what was changed, and include a "## Checklist" section with checkboxes for the three required items: applying an appropriate label, confirming documentation updates, and confirming test updates. Even though this appears to be an auto-generated Dependabot PR, following the template ensures consistency and captures important information about the impact of these breaking version changes on the project.
✅ Passed checks (2 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
Title Check ✅ Passed The title clearly and accurately describes the primary change by indicating a bump of the OpenTelemetry group dependencies with six updates, which aligns with the six package version changes in the pull request. It is concise and directly related to the changes without introducing off-topic terms or unnecessary details. Therefore, the title meets the criteria for summarizing the main change.

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 12c5787 and d9de5b6.

📒 Files selected for processing (1)
  • packages/app/context-fastify-plugins/package.json (1 hunks)

Comment on lines 40 to 45
"@opentelemetry/exporter-trace-otlp-grpc": "0.203.0",
"@opentelemetry/instrumentation": "0.203.0",
"@opentelemetry/resources": "2.0.1",
"@opentelemetry/sdk-trace-base": "2.0.1",
"@opentelemetry/sdk-trace-node": "2.0.1",
"@opentelemetry/semantic-conventions": "1.36.0",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Breaking-version bumps require explicit Node ≥ 18.19 & ES2022 compilation – guard with an engines field and review your tsconfig

The OpenTelemetry packages you just moved to (0.203.x / 2.0.x) officially drop Node 14/16 and raise the compilation target to ES2022.
Your package.json currently does not communicate this requirement to downstream consumers or CI runners, and the repo’s build script may still rely on an older target in tsconfig.build.json.

Action items:

  1. Expose the minimum runtime via the engines key so npm/pnpm/yarn can refuse unsupported environments.
  2. Make sure tsconfig.build.json (and any Jest/Vitest transforms) compile to ES2022 or higher.
  3. Verify that your CI matrix and README match the new floor.

Suggested patch:

   "license": "Apache-2.0",
   "type": "module",
+  "engines": {
+    "node": ">=18.19.0"
+  },
   "main": "./dist/index.js",

After adding the field, run the build locally with Node 18/20 to confirm no SyntaxError surfaces from newer syntax (e.g., ?., ??=, top-level await).
Finally, re-run vitest to ensure instrumentation APIs removed in 2.0 don’t break your tracing setup.


To verify the Node.js requirement and your TS compile target, let’s pull both from the repo and upstream docs:


🏁 Script executed:

#!/bin/bash
# Locate tsconfig.build.json and show its "target" setting
fd tsconfig.build.json | while read file; do
  echo "=== $file ==="
  sed -n '1,200p' "$file" | grep -n '"target"'
done

Length of output: 4767


🌐 Web query:

What Node.js versions are supported by @opentelemetry/[email protected]?

💡 Result:

@opentelemetry/[email protected] supports only Node.js Active or Maintenance LTS versions, with a specifically raised minimum version of Node.js 18.19.0 or higher, or Node.js 20.6.0 or higher[2][6][7]. This means Node.js 14 and 16 are no longer supported.

Supported Node.js versions for @opentelemetry/[email protected]:

  • Node.js 18.19.0 or newer (18.x)
  • Node.js 20.6.0 or newer (20.x)
  • Node.js 22.x (current as of mid-2025)

Only these versions are tested and officially supported by OpenTelemetry; earlier Node.js versions may work but are not guaranteed or tested[5][6][7].

Key points:

  • Node.js <18.19.0 and <20.6.0 are not supported—support for Node.js 14 and 16 was dropped in SDK 2.x[2][6].
  • These requirements align with the official OpenTelemetry documentation and release notes[2][5][6][7].

No support is provided for Node.js versions that are not Active or Maintenance LTS releases as defined by the Node.js project.

Citations:


Require Node ≥18.19 & ES2022 compile target for OpenTelemetry v2.x

OpenTelemetry v2.x drops Node 14/16 support and emits ES2022+ syntax. We must enforce the new minimum runtime and update our build config accordingly.

Action items:

  • Add an engines field to packages/app/context-fastify-plugins/package.json:
       "type": "module",
    +  "engines": {
    +    "node": ">=18.19.0"
    +  },
       "main": "./dist/index.js",
  • Update tsconfig.build.json (and any Jest/Vitest transforms) to compile to ES2022 or higher:
       {
         "extends": "../../tsconfig.json",
         "compilerOptions": {
    +      "target": "ES2022",
           // …
         }
       }
  • Ensure your CI matrix and README reflect Node 18.19+ (and 20.6+/22.x) as the new minimum.
  • Run the build and tests locally on Node 18/20 to catch any new-syntax or instrumentation issues.

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents
In packages/app/context-fastify-plugins/package.json around lines 40 to 45, add
an "engines" field specifying Node version 18.19 or higher to enforce the
minimum runtime required by OpenTelemetry v2.x. Update tsconfig.build.json and
any Jest or Vitest transform configurations to target ES2022 or above to match
the emitted syntax. Also, update the CI configuration and README to reflect Node
18.19+ as the minimum supported version. Finally, run builds and tests locally
on Node 18 and 20 to verify compatibility and catch any syntax or
instrumentation issues.

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch 2 times, most recently from 0e71696 to 9e5cd8c Compare August 11, 2025 17:09
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch from 9e5cd8c to 44b6e8d Compare August 18, 2025 22:55
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch from 44b6e8d to 0a22d68 Compare September 8, 2025 12:24
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch 2 times, most recently from 438d7c3 to be3c047 Compare September 22, 2025 12:09
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch 2 times, most recently from 6983829 to aad4cf3 Compare October 13, 2025 12:41
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch from aad4cf3 to 748e2b4 Compare October 20, 2025 12:55
Bumps the opentelemetry group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@opentelemetry/exporter-trace-otlp-grpc](https://github.com/open-telemetry/opentelemetry-js) | `0.57.2` | `0.200.0` |
| [@opentelemetry/instrumentation](https://github.com/open-telemetry/opentelemetry-js) | `0.57.2` | `0.200.0` |
| [@opentelemetry/resources](https://github.com/open-telemetry/opentelemetry-js) | `1.30.1` | `2.0.0` |
| [@opentelemetry/sdk-trace-base](https://github.com/open-telemetry/opentelemetry-js) | `1.30.1` | `2.0.0` |
| [@opentelemetry/sdk-trace-node](https://github.com/open-telemetry/opentelemetry-js) | `1.30.1` | `2.0.0` |
| [@opentelemetry/semantic-conventions](https://github.com/open-telemetry/opentelemetry-js) | `1.30.0` | `1.32.0` |



Updates `@opentelemetry/exporter-trace-otlp-grpc` from 0.57.2 to 0.200.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@experimental/v0.57.2...experimental/v0.200.0)

Updates `@opentelemetry/instrumentation` from 0.57.2 to 0.200.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@experimental/v0.57.2...experimental/v0.200.0)

Updates `@opentelemetry/resources` from 1.30.1 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.30.1...v2.0.0)

Updates `@opentelemetry/sdk-trace-base` from 1.30.1 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.30.1...v2.0.0)

Updates `@opentelemetry/sdk-trace-node` from 1.30.1 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.30.1...v2.0.0)

Updates `@opentelemetry/semantic-conventions` from 1.30.0 to 1.32.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.30.0...semconv/v1.32.0)

---
updated-dependencies:
- dependency-name: "@opentelemetry/exporter-trace-otlp-grpc"
  dependency-version: 0.200.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: opentelemetry
- dependency-name: "@opentelemetry/instrumentation"
  dependency-version: 0.200.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: opentelemetry
- dependency-name: "@opentelemetry/resources"
  dependency-version: 2.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: opentelemetry
- dependency-name: "@opentelemetry/sdk-trace-base"
  dependency-version: 2.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: opentelemetry
- dependency-name: "@opentelemetry/sdk-trace-node"
  dependency-version: 2.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: opentelemetry
- dependency-name: "@opentelemetry/semantic-conventions"
  dependency-version: 1.32.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: opentelemetry
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/opentelemetry-da5697932a branch from 748e2b4 to 45eecb8 Compare October 27, 2025 13:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant