Skip to content

Conversation

dependabot[bot]
Copy link
Contributor

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

Bumps the opentelemetry group with 5 updates in the /auth directory:

Package From To
@opentelemetry/exporter-trace-otlp-grpc 0.57.2 0.200.0
@opentelemetry/instrumentation 0.57.2 0.200.0
@opentelemetry/instrumentation-express 0.47.1 0.48.0
@opentelemetry/instrumentation-http 0.57.2 0.200.0
@opentelemetry/sdk-node 0.57.2 0.200.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

📚 Documentation

🏠 Internal

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

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

📚 Documentation

🏠 Internal

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

... (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-express from 0.47.1 to 0.48.0

Release notes

Sourced from @​opentelemetry/instrumentation-express's releases.

instrumentation-koa: v0.48.0

0.48.0 (2025-03-18)

⚠ BREAKING CHANGES

  • chore!: Update to 2.x and 0.200.x @opentelemetry/* packages from opentelemetry-js.git per 2.x upgrade guide
    • 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).

Bug Fixes

  • deps: update otel core experimental to ^0.57.2 (#2716) (d2a9a20)

Miscellaneous Chores

Dependencies

  • The following workspace dependencies were updated
    • devDependencies
      • @​opentelemetry/contrib-test-utils bumped from ^0.45.1 to ^0.46.0

instrumentation-ioredis: v0.48.0

0.48.0 (2025-03-18)

⚠ BREAKING CHANGES

  • chore!: Update to 2.x and 0.200.x @opentelemetry/* packages from opentelemetry-js.git per 2.x upgrade guide
    • 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).

Bug Fixes

  • deps: update otel core experimental to ^0.57.2 (#2716) (d2a9a20)

Miscellaneous Chores

Dependencies

... (truncated)

Commits

Updates @opentelemetry/instrumentation-http from 0.57.2 to 0.200.0

Release notes

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

📚 Documentation

🏠 Internal

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

... (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-node from 0.57.2 to 0.200.0

Release notes

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

Unreleased

💥 Breaking Changes

🚀 Features

🐛 Bug Fixes

📚 Documentation

🏠 Internal

...

Description has been truncated

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

@dependabot dependabot bot added dependencies javascript Pull requests that update Javascript code labels Mar 19, 2025
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/auth/opentelemetry-c459bee5b7 branch 2 times, most recently from 350e741 to 375abf0 Compare March 26, 2025 06:32
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/auth/opentelemetry-c459bee5b7 branch from 375abf0 to 6951fa5 Compare April 16, 2025 06:09
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/auth/opentelemetry-c459bee5b7 branch from 6951fa5 to 2a052ad Compare April 24, 2025 06:21
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/auth/opentelemetry-c459bee5b7 branch 4 times, most recently from 6de5757 to f1b3d02 Compare May 21, 2025 06:30
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/auth/opentelemetry-c459bee5b7 branch 3 times, most recently from 433c348 to 346a612 Compare June 5, 2025 06:43
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/auth/opentelemetry-c459bee5b7 branch 2 times, most recently from cb9fcbc to df6fb15 Compare June 17, 2025 06:17
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/auth/opentelemetry-c459bee5b7 branch 2 times, most recently from 48f7c24 to c9e77d0 Compare July 1, 2025 08:50
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/auth/opentelemetry-c459bee5b7 branch 2 times, most recently from 8522897 to 9b36c6b Compare July 9, 2025 06:07
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/auth/opentelemetry-c459bee5b7 branch 5 times, most recently from f7bd77a to 1c7eba6 Compare July 21, 2025 08:56
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/auth/opentelemetry-c459bee5b7 branch 5 times, most recently from 9671921 to b6ee730 Compare July 29, 2025 07:51
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/auth/opentelemetry-c459bee5b7 branch 4 times, most recently from 19b7aa9 to 871ee96 Compare August 6, 2025 07:31
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/auth/opentelemetry-c459bee5b7 branch from 871ee96 to 4f85405 Compare August 11, 2025 11:19
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/auth/opentelemetry-c459bee5b7 branch 2 times, most recently from 20c0ed1 to 6aacf41 Compare August 25, 2025 10:33
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/auth/opentelemetry-c459bee5b7 branch from 6aacf41 to 1a56d9f Compare September 8, 2025 06:02
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/auth/opentelemetry-c459bee5b7 branch 3 times, most recently from e145082 to e5c0071 Compare September 22, 2025 06:05
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/auth/opentelemetry-c459bee5b7 branch 2 times, most recently from 17039fd to 05d05b9 Compare October 6, 2025 06:02
Bumps the opentelemetry group with 5 updates in the /auth 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/instrumentation-express](https://github.com/open-telemetry/opentelemetry-js-contrib) | `0.47.1` | `0.48.0` |
| [@opentelemetry/instrumentation-http](https://github.com/open-telemetry/opentelemetry-js) | `0.57.2` | `0.200.0` |
| [@opentelemetry/sdk-node](https://github.com/open-telemetry/opentelemetry-js) | `0.57.2` | `0.200.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/instrumentation-express` from 0.47.1 to 0.48.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-js-contrib/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/CHANGELOG.md)
- [Commits](open-telemetry/opentelemetry-js-contrib@instrumentation-pg-v0.47.1...instrumentation-pg-v0.48.0)

Updates `@opentelemetry/instrumentation-http` 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/sdk-node` 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)

---
updated-dependencies:
- dependency-name: "@opentelemetry/exporter-trace-otlp-grpc"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: opentelemetry
- dependency-name: "@opentelemetry/instrumentation"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: opentelemetry
- dependency-name: "@opentelemetry/instrumentation-express"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: opentelemetry
- dependency-name: "@opentelemetry/instrumentation-http"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: opentelemetry
- dependency-name: "@opentelemetry/sdk-node"
  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/auth/opentelemetry-c459bee5b7 branch from 05d05b9 to db8d236 Compare October 13, 2025 06:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies javascript Pull requests that update Javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant