[Snyk] Upgrade @opentelemetry/instrumentation from 0.41.1 to 0.54.2

[X-oss-byte]

Snyk has created this PR to upgrade @opentelemetry/instrumentation from 0.41.1 to 0.54.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 20 versions ahead of your current version.

• The recommended version was released on a month ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Regular Expression Denial of Service (ReDoS) SNYK-JS-CROSSSPAWN-8303230	542	Proof of Concept
	Arbitrary Code Execution SNYK-JS-IMPORTINTHEMIDDLE-5826054	542	No Known Exploit
	Regular Expression Denial of Service (ReDoS) SNYK-JS-FASTXMLPARSER-7573289	542	No Known Exploit
	Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116	542	Proof of Concept

Release notes

Package name: @opentelemetry/instrumentation

• 0.54.2 - 2024-11-07
  

  0.54.2

  🐛 (Bug Fix)

  • fix(instrumentation): Fix wrapping ESM files with absolute path #5094 @ serkan-ozal
• 0.54.1 - 2024-11-05
  

  0.54.1

  🐛 (Bug Fix)

  • fix(instrumentation-http): skip malformed forwarded headers. #5095 @ pmlanger
• 0.54.0 - 2024-10-23
  

  0.54.0

  💥 Breaking Change

  • feat(exporter--otlp-)!: rewrite exporter config logic for testability #4971 @ pichlermarc
    • (user-facing) getDefaultUrl was intended for internal use has been removed from all exporters
    • (user-facing) getUrlFromConfig was intended for internal use and has been removed from all exporters
    • (user-facing) hostname was intended for internal use and has been removed from all exporters
    • (user-facing) url was intended for internal use and has been removed from all exporters
    • (user-facing) timeoutMillis was intended for internal use and has been removed from all exporters
    • (user-facing) onInit was intended for internal use and has been removed from all exporters
    • (user-facing) OTLP exporter config headers type changed from Partial<Record<string, unknown>> to Record<string, string>
  • feat(otlp-exporter-base)!: do not export functions that are intended for internal use #4971 @ pichlermarc
    • Drops the following functions and types that were intended for internal use from the package exports:
      • parseHeaders
      • appendResourcePathToUrl
      • appendResourcePathToUrlIfNeeded
      • configureExporterTimeout
      • invalidTimeout
  • feat(instrumentation-http)!: remove long deprecated options #5085 @ pichlermarc
    • ignoreIncomingPaths has been removed, use the more versatile ignoreIncomingRequestHook instead.
    • ignoreOutgoingUrls has been removed, use the more versatile ignoreOutgoingRequestHook instead.
    • isIgnored utility function was intended for internal use and has been removed without replacement.

  🚀 (Enhancement)

  • feat(api-logs): Add delegating no-op logger provider #4861 @ hectorhdzg
  • feat(instrumentation-http): Add support for Semantic Conventions 1.27+ #4940 #4978 #5026 @ dyladan
    • Applies to client and server spans and metrics
    • Generate spans and metrics compliant with Semantic Conventions 1.27+ when OTEL_SEMCONV_STABILITY_OPT_IN contains http or http/dup
    • Generate spans and metrics backwards compatible with previous attributes when OTEL_SEMCONV_STABILITY_OPT_IN contains http/dup or DOES NOT contain http

  🐛 (Bug Fix)

  • fix(sampler-jaeger-remote): fixes an issue where package could emit unhandled promise rejections @ Just-Sieb
  • fix(otlp-grpc-exporter-base): default compression to 'none' if env vars OTEL_EXPORTER_OTLP_TRACES_COMPRESSION and OTEL_EXPORTER_OTLP_COMPRESSION are falsy @ sjvans
  • fix(sdk-events): remove devDependencies to old @ opentelemetry/api-logs@0.52.0, @ opentelemetry/api-events@0.52.0 packages #5013 @ pichlermarc
  • fix(sdk-logs): remove devDependencies to old @ opentelemetry/api-logs@0.52.0 #5013 @ pichlermarc
  • fix(sdk-logs): align LogRecord#setAttribute type with types from @ opentelemetry/api-logs@0.53.0 #5013 @ pichlermarc
  • fix(exporter--otlp-): fixes a bug where signal-specific environment variables would not be applied and the trace-specific one was used instead #4971 @ pichlermarc
    • Fixes:
      • OTEL_EXPORTER_OTLP_METRICS_COMPRESSION
      • OTEL_EXPORTER_OTLP_LOGS_COMPRESSION
      • OTEL_EXPORTER_OTLP_METRICS_CLIENT_CERTIFICATE
      • OTEL_EXPORTER_OTLP_LOGS_CLIENT_CERTIFICATE
      • OTEL_EXPORTER_OTLP_METRICS_CLIENT_KEY
      • OTEL_EXPORTER_OTLP_LOGS_CLIENT_KEY
      • OTEL_EXPORTER_OTLP_METRICS_INSECURE
      • OTEL_EXPORTER_OTLP_LOGS_INSECURE
  • fix(sdk-node): use warn instead of error on unknown OTEL_NODE_RESOURCE_DETECTORS values #5034
  • fix(exporter-logs-otlp-proto): Use correct config type in Node constructor
  • fix(instrumentation-http): Fix instrumentation of http.get, http.request, https.get, and https.request when used from ESM code and imported via the import defaultExport from 'http' style. #5024 @ trentm

  🏠 (Internal)

  • refactor(exporter-prometheus): replace MetricAttributes and MetricAttributeValues with Attributes and AttributeValues #4993

  • refactor(browser-detector): replace ResourceAttributes with Attributes #5004

  • refactor(sdk-logs): replace ResourceAttributes with Attributes #5005 @ david-luna

• 0.53.0 - 2024-08-28
• 0.52.1 - 2024-06-20
• 0.52.0 - 2024-06-05
• 0.51.1 - 2024-05-07
• 0.51.0 - 2024-04-24
• 0.50.0 - 2024-04-03
• 0.49.1 - 2024-02-29
• 0.49.0 - 2024-02-29
• 0.48.0 - 2024-01-26
• 0.47.0 - 2024-01-15
• 0.46.0 - 2023-12-14
• 0.45.1 - 2023-11-08
• 0.45.0 - 2023-11-07
• 0.44.0 - 2023-10-10
• 0.43.0 - 2023-09-12
• 0.42.0 - 2023-09-11
• 0.41.2 - 2023-08-08
• 0.41.1 - 2023-07-24

from @opentelemetry/instrumentation GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Summary by Sourcery

Build:

• Upgrade @opentelemetry/instrumentation from version 0.41.1 to 0.54.2 in package.json.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5a2a071

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR upgrades the @opentelemetry/instrumentation package from version 0.41.1 to 0.54.2 to address several security vulnerabilities and incorporate the latest features and bug fixes. The upgrade spans 20 versions and includes breaking changes related to exporter configurations, HTTP instrumentation options, and internal API changes.

Class diagram for changes in @opentelemetry/instrumentation

classDiagram
    class ExporterConfig {
        - getDefaultUrl()
        - getUrlFromConfig()
        - hostname
        - url
        - timeoutMillis
        - onInit
        headers: Record<string, string>
    }
    class InstrumentationHttp {
        - ignoreIncomingPaths
        - ignoreOutgoingUrls
        - isIgnored
        + ignoreIncomingRequestHook()
        + ignoreOutgoingRequestHook()
    }
    note for ExporterConfig "Breaking changes: Removed internal methods and changed headers type"
    note for InstrumentationHttp "Breaking changes: Removed deprecated options and added new hooks"

Loading

File-Level Changes

Change	Details	Files
Security vulnerability fixes	Fix high severity Regular Expression Denial of Service (ReDoS) vulnerability Fix high severity Arbitrary Code Execution vulnerability Fix medium severity Regular Expression Denial of Service (ReDoS) vulnerability Fix medium severity Missing Release of Resource vulnerability	package.json
Breaking changes in configuration and API	Remove internal use functions and types from package exports Remove deprecated HTTP instrumentation options Change OTLP exporter headers type to be more strict Rewrite exporter config logic for better testability	package.json
Feature enhancements and bug fixes	Add support for Semantic Conventions 1.27+ Fix wrapping ESM files with absolute path Fix handling of malformed forwarded headers Add delegating no-op logger provider	package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. Here's why:

• It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
• We don't review packaging changes - Let us know if you'd like us to change this.