chore(deps-dev): bump @opentelemetry/instrumentation-http from 0.53.0 to 0.200.0

[dependabot]

Bumps @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 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
  • 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

... (truncated)

Commits

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

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

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