chore(deps): bump the observability group with 17 updates by dependabot[bot] · Pull Request #31 · AIM-Intelligence/AIM-Tracer-KB

dependabot · 2025-04-02T17:21:32Z

Bumps the observability group with 17 updates:

Package	From	To
@opentelemetry/core	`1.26.0`	`2.0.0`
@opentelemetry/exporter-trace-otlp-proto	`0.53.0`	`0.200.0`
@opentelemetry/instrumentation	`0.53.0`	`0.200.0`
@opentelemetry/instrumentation-aws-sdk	`0.44.0`	`0.50.0`
@opentelemetry/instrumentation-http	`0.53.0`	`0.200.0`
@opentelemetry/instrumentation-ioredis	`0.43.0`	`0.48.0`
@opentelemetry/instrumentation-winston	`0.40.0`	`0.45.0`
@opentelemetry/resource-detector-aws	`1.6.2`	`2.0.0`
@opentelemetry/resource-detector-container	`0.4.2`	`0.7.0`
@opentelemetry/resources	`1.26.0`	`2.0.0`
@opentelemetry/sdk-node	`0.53.0`	`0.200.0`
@opentelemetry/sdk-trace-base	`1.26.0`	`2.0.0`
@opentelemetry/sdk-trace-node	`1.26.0`	`2.0.0`
@prisma/instrumentation	`6.3.0`	`6.5.0`
@sentry/nextjs	`8.55.0`	`9.10.1`
dd-trace	`5.36.0`	`5.45.0`
@opentelemetry/instrumentation-express	`0.43.0`	`0.48.0`

Updates @opentelemetry/core from 1.26.0 to 2.0.0

Release notes

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

for notes on migrating to 2.x / 0.200.x see the upgrade guide

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/core'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

for notes on migrating to 2.x / 0.200.x see the upgrade guide

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/exporter-trace-otlp-proto from 0.53.0 to 0.200.0

Release notes

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

for notes on migrating to 2.x / 0.200.x see the upgrade guide

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-proto'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

📚 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

for notes on migrating to 2.x / 0.200.x see the upgrade guide

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

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

for notes on migrating to 2.x / 0.200.x see the upgrade guide

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

📚 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

for notes on migrating to 2.x / 0.200.x see the upgrade guide

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

... (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-aws-sdk from 0.44.0 to 0.50.0

Release notes

Sourced from @opentelemetry/instrumentation-aws-sdk's releases.

instrumentation-user-interaction: v0.45.0

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

update to JS SDK 2.x (#2738) (7fb4ba3)

instrumentation-long-task: v0.45.0

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

update to JS SDK 2.x (#2738) (7fb4ba3)

instrumentation-document-load: v0.45.0

0.45.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).

... (truncated)

Commits

3ef5205 chore: release main (#2586)
aa46705 feat(deps): update deps matching '@opentelemetry/*' (#2608)
2dc302c ci: do not mark propagator-aws-xray as umaintained (#2606)
37ea847 feat(deps): lock file maintenance (#2605)
91c9089 feat: report url for lambda invoked via api gateway (#2404)
ba615db chore(deps): update dependency mongoose to v6.13.5 [security] (#2595)
d4569c3 feat(deps): lock file maintenance (#2596)
6158af0 feat(deps): lock file maintenance (#2225)
30d668e chore(deps): lock file maintenance (#2594)
2e0cbdf feat!: widen peer dependency range to include zone.js v0.15.0 (#2571)
Additional commits viewable in compare view

Updates @opentelemetry/instrumentation-http from 0.53.0 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

for notes on migrating to 2.x / 0.200.x see the upgrade guide

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...
Description has been truncated

Bumps the observability group with 17 updates: | Package | From | To | | --- | --- | --- | | [@opentelemetry/core](https://github.com/open-telemetry/opentelemetry-js) | `1.26.0` | `2.0.0` | | [@opentelemetry/exporter-trace-otlp-proto](https://github.com/open-telemetry/opentelemetry-js) | `0.53.0` | `0.200.0` | | [@opentelemetry/instrumentation](https://github.com/open-telemetry/opentelemetry-js) | `0.53.0` | `0.200.0` | | [@opentelemetry/instrumentation-aws-sdk](https://github.com/open-telemetry/opentelemetry-js-contrib) | `0.44.0` | `0.50.0` | | [@opentelemetry/instrumentation-http](https://github.com/open-telemetry/opentelemetry-js) | `0.53.0` | `0.200.0` | | [@opentelemetry/instrumentation-ioredis](https://github.com/open-telemetry/opentelemetry-js-contrib) | `0.43.0` | `0.48.0` | | [@opentelemetry/instrumentation-winston](https://github.com/open-telemetry/opentelemetry-js-contrib) | `0.40.0` | `0.45.0` | | [@opentelemetry/resource-detector-aws](https://github.com/open-telemetry/opentelemetry-js-contrib) | `1.6.2` | `2.0.0` | | [@opentelemetry/resource-detector-container](https://github.com/open-telemetry/opentelemetry-js-contrib) | `0.4.2` | `0.7.0` | | [@opentelemetry/resources](https://github.com/open-telemetry/opentelemetry-js) | `1.26.0` | `2.0.0` | | [@opentelemetry/sdk-node](https://github.com/open-telemetry/opentelemetry-js) | `0.53.0` | `0.200.0` | | [@opentelemetry/sdk-trace-base](https://github.com/open-telemetry/opentelemetry-js) | `1.26.0` | `2.0.0` | | [@opentelemetry/sdk-trace-node](https://github.com/open-telemetry/opentelemetry-js) | `1.26.0` | `2.0.0` | | [@prisma/instrumentation](https://github.com/prisma/prisma/tree/HEAD/packages/instrumentation) | `6.3.0` | `6.5.0` | | [@sentry/nextjs](https://github.com/getsentry/sentry-javascript) | `8.55.0` | `9.10.1` | | [dd-trace](https://github.com/DataDog/dd-trace-js) | `5.36.0` | `5.45.0` | | [@opentelemetry/instrumentation-express](https://github.com/open-telemetry/opentelemetry-js-contrib) | `0.43.0` | `0.48.0` | Updates `@opentelemetry/core` from 1.26.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.26.0...v2.0.0) Updates `@opentelemetry/exporter-trace-otlp-proto` from 0.53.0 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.53.0...experimental/v0.200.0) Updates `@opentelemetry/instrumentation` from 0.53.0 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.53.0...experimental/v0.200.0) Updates `@opentelemetry/instrumentation-aws-sdk` from 0.44.0 to 0.50.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@contrib-test-utils-v0.44.0...instrumentation-pg-v0.50.0) Updates `@opentelemetry/instrumentation-http` from 0.53.0 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.53.0...experimental/v0.200.0) Updates `@opentelemetry/instrumentation-ioredis` from 0.43.0 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@contrib-test-utils-v0.43.0...instrumentation-pg-v0.48.0) Updates `@opentelemetry/instrumentation-winston` from 0.40.0 to 0.45.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@sql-common-v0.40.0...instrumentation-pg-v0.45.0) Updates `@opentelemetry/resource-detector-aws` from 1.6.2 to 2.0.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@resource-detector-aws-v1.6.2...propagator-aws-xray-v2.0.0) Updates `@opentelemetry/resource-detector-container` from 0.4.2 to 0.7.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@resource-detector-instana-v0.4.2...v0.7.0) Updates `@opentelemetry/resources` from 1.26.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.26.0...v2.0.0) Updates `@opentelemetry/sdk-node` from 0.53.0 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.53.0...experimental/v0.200.0) Updates `@opentelemetry/sdk-trace-base` from 1.26.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.26.0...v2.0.0) Updates `@opentelemetry/sdk-trace-node` from 1.26.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.26.0...v2.0.0) Updates `@prisma/instrumentation` from 6.3.0 to 6.5.0 - [Release notes](https://github.com/prisma/prisma/releases) - [Commits](https://github.com/prisma/prisma/commits/6.5.0/packages/instrumentation) Updates `@sentry/nextjs` from 8.55.0 to 9.10.1 - [Release notes](https://github.com/getsentry/sentry-javascript/releases) - [Changelog](https://github.com/getsentry/sentry-javascript/blob/develop/CHANGELOG.md) - [Commits](getsentry/sentry-javascript@8.55.0...9.10.1) Updates `dd-trace` from 5.36.0 to 5.45.0 - [Release notes](https://github.com/DataDog/dd-trace-js/releases) - [Commits](DataDog/dd-trace-js@v5.36.0...v5.45.0) Updates `@opentelemetry/instrumentation-express` from 0.43.0 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@contrib-test-utils-v0.43.0...instrumentation-pg-v0.48.0) --- updated-dependencies: - dependency-name: "@opentelemetry/core" dependency-type: direct:production update-type: version-update:semver-major dependency-group: observability - dependency-name: "@opentelemetry/exporter-trace-otlp-proto" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: observability - dependency-name: "@opentelemetry/instrumentation" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: observability - dependency-name: "@opentelemetry/instrumentation-aws-sdk" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: observability - dependency-name: "@opentelemetry/instrumentation-http" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: observability - dependency-name: "@opentelemetry/instrumentation-ioredis" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: observability - dependency-name: "@opentelemetry/instrumentation-winston" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: observability - dependency-name: "@opentelemetry/resource-detector-aws" dependency-type: direct:production update-type: version-update:semver-major dependency-group: observability - dependency-name: "@opentelemetry/resource-detector-container" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: observability - dependency-name: "@opentelemetry/resources" dependency-type: direct:production update-type: version-update:semver-major dependency-group: observability - dependency-name: "@opentelemetry/sdk-node" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: observability - dependency-name: "@opentelemetry/sdk-trace-base" dependency-type: direct:production update-type: version-update:semver-major dependency-group: observability - dependency-name: "@opentelemetry/sdk-trace-node" dependency-type: direct:production update-type: version-update:semver-major dependency-group: observability - dependency-name: "@prisma/instrumentation" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: observability - dependency-name: "@sentry/nextjs" dependency-type: direct:production update-type: version-update:semver-major dependency-group: observability - dependency-name: dd-trace dependency-type: direct:production update-type: version-update:semver-minor dependency-group: observability - dependency-name: "@opentelemetry/instrumentation-express" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: observability ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot · 2025-05-01T16:40:26Z

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Apr 2, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): bump the observability group with 17 updates#31

chore(deps): bump the observability group with 17 updates#31
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/observability-ea38fb9131

dependabot bot commented on behalf of github Apr 2, 2025 •

edited

Loading

Uh oh!

dependabot bot commented on behalf of github May 1, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

dependabot bot commented on behalf of github Apr 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

v2.0.0

2.0.0

Summary

💥 Breaking Change

2.0.0

Summary

💥 Breaking Change

experimental/v0.200.0

0.200.0

Summary

💥 Breaking Change

🚀 (Enhancement)

🐛 (Bug Fix)

🏠 (Internal)

CHANGELOG

Unreleased

💥 Breaking Changes

🚀 Features

🐛 Bug Fixes

📚 Documentation

🏠 Internal

2.0.0

Summary

💥 Breaking Change

experimental/v0.200.0

0.200.0

Summary

💥 Breaking Change

🚀 (Enhancement)

🐛 (Bug Fix)

🏠 (Internal)

CHANGELOG

Unreleased

💥 Breaking Changes

🚀 Features

🐛 Bug Fixes

📚 Documentation

🏠 Internal

2.0.0

Summary

💥 Breaking Change

instrumentation-user-interaction: v0.45.0

0.45.0 (2025-03-18)

⚠ BREAKING CHANGES

Bug Fixes

Miscellaneous Chores

instrumentation-long-task: v0.45.0

0.45.0 (2025-03-18)

⚠ BREAKING CHANGES

Bug Fixes

Miscellaneous Chores

instrumentation-document-load: v0.45.0

0.45.0 (2025-03-18)

⚠ BREAKING CHANGES

experimental/v0.200.0

0.200.0

Summary

💥 Breaking Change

Uh oh!

dependabot bot commented on behalf of github May 1, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

dependabot bot commented on behalf of github Apr 2, 2025 •

edited

Loading