Skip to content

Conversation

@shewood
Copy link
Contributor

@shewood shewood commented Oct 28, 2025

snyk-top-banner

Snyk has created this PR to upgrade @opentelemetry/exporter-metrics-otlp-proto from 0.204.0 to 0.206.0.

ℹ️ 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 2 versions ahead of your current version.

  • The recommended version was released 22 days ago.

Release notes
Package name: @opentelemetry/exporter-metrics-otlp-proto
  • 0.206.0 - 2025-10-06

    0.206.0

    🚀 Features

    • feat(otlp-transformer): add span flags support for isRemote property #5910 @ nikhilmantri0902
    • feat(sampler-composite): Added experimental implementations of draft composite sampling spec #5839 @ anuraaga
    • feat(opentelemetry-configuration): add more attributes to config model #5826 @ maryliag
    • feat(opentelemetry-configuration): Parse of Configuration File #5875 @ maryliag
    • feat(opentelemetry-configuration): parse of array objects on configuration file #5947 @ maryliag
    • feat(opentelemetry-configuration): parse of environment variables on configuration file #5947 @ maryliag

    🐛 Bug Fixes

    • fix(instrumentation-http): respect requireParent flag when INVALID_SPAN_CONTEXT is used #4788 @ reberhardt7
    • fix(otlp-transformer): trunc hrTime to int for nanos converting #5924 @ blumamir

    🏠 Internal

    • refactor(otlp-exporter-base): use get*FromEnv() for otlp exporter config. #5583 @ weyert
  • 0.205.0 - 2025-09-10

    0.205.0

    💥 Breaking Changes

    • fix(otlp-exporter-base)!: split node and browser config types in two #5917 @ pichlermarc
      • Fixes a bug where Node.js modules would be incorrectly used in the instantiation of a web-targeted exporter
      • Breaking changes:
        • (user-facing) createOtlpHttpExportDelegate(OtlpHttpConfiguration) has been changed to take a different, but identical type OtlpNodeHttpConfiguration to differentiate it from the web-targeted exporters
        • (user-facing) convertLegacyHttpOptions(...) now returns OtlpNodeHttpConfiguration, the returned object's contents remain identical.
        • (user-facing) agentFactory has been dropped from OtlpHttpConfiguration as it is node-specific and is now part of OtlpNodeHttpConfiguration instead
  • 0.204.0 - 2025-09-04

    0.204.0

    💥 Breaking Changes

    • feat(api-logs)!: Marked private methods as "conventionally private". #5789
    • feat(exporter-otlp-*): support custom HTTP agents #5719 @ raphael-theriault-swi
      • OtlpHttpConfiguration.agentOptions has been removed and functionality has been rolled into OtlpHttpConfiguration.agentFactory
        • (old) { agentOptions: myOptions }
        • (new) { agentFactory: httpAgentFactoryFromOptions(myOptions) }

    🚀 Features

    • feat(otlp-exporter-base): Add fetch transport for fetch-only environments like service workers. #5807
      • when using headers, the Browser exporter now prefers fetch over XMLHttpRequest if present. Sending via XMLHttpRequest will be removed in a future release.
    • feat(opentelemetry-configuration): creation of basic ConfigProvider #5809 @ maryliag
    • feat(opentelemetry-configuration): creation of basic FileConfigProvider #5863 @ maryliag
    • feat(sdk-node): Add support for multiple metric readers via the new metricReaders option in NodeSDK configuration. Users can now register multiple metric readers (e.g., Console, Prometheus) directly through the NodeSDK constructor. The old metricReader (singular) option is now deprecated and will show a warning if used, but remains supported for backward compatibility. Comprehensive tests and documentation have been added. #5760
      • Migration:

        • Before:

          const sdk = new NodeSDK({ metricReader: myMetricReader });
        • After:

          const sdk = new NodeSDK({ metricReaders: [myMetricReader] });
      • Users should migrate to the new metricReaders array option for future compatibility. The old option will be removed in an upcoming experimental version.

    • feat(instrumentation-http): Added support for redacting specific url query string values and url credentials #5743 @ rads-1996

    🐛 Bug Fixes

    • fix(otlp-exporter-base): prioritize esnext export condition as it is more specific #5458
    • fix(otlp-exporter-base): consider relative urls as valid in browser environments #5807
    • fix(instrumentation-fetch): Use ESM version of semconv instead of CJS. Users expecting mixed ESM and CJS modules will now only get ESM modules. #5878 @ overbalance

    🏠 Internal

from @opentelemetry/exporter-metrics-otlp-proto 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.

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:

…to 0.206.0

Snyk has created this PR to upgrade @opentelemetry/exporter-metrics-otlp-proto from 0.204.0 to 0.206.0.

See this package in npm:
@opentelemetry/exporter-metrics-otlp-proto

See this project in Snyk:
https://app.snyk.io/org/p0nder0sa/project/60ffc669-57aa-416f-923d-9c5e8c2c64de?utm_source=github&utm_medium=referral&page=upgrade-pr
@shewood shewood requested a review from a team as a code owner October 28, 2025 11:45
@github-actions
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants