[Snyk] Upgrade @opentelemetry/otlp-transformer from 0.203.0 to 0.205.0 #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade @opentelemetry/otlp-transformer from 0.203.0 to 0.205.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 24 days ago.
Release notes
Package name: @opentelemetry/otlp-transformer
-
0.205.0 - 2025-09-10
- 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)
- (user-facing)
- (user-facing)
-
0.204.0 - 2025-09-04
- feat(api-logs)!: Marked private methods as "conventionally private". #5789
- feat(exporter-otlp-*): support custom HTTP agents #5719 @ raphael-theriault-swi
- (old)
- (new)
- feat(otlp-exporter-base): Add fetch transport for fetch-only environments like service workers. #5807
- when using headers, the Browser exporter now prefers
- 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
-
-
-
-
- feat(instrumentation-http): Added support for redacting specific url query string values and url credentials #5743 @ rads-1996
- fix(otlp-exporter-base): prioritize
- 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
- refactor(otlp-exporter-base): use getStringFromEnv instead of process.env #5594 @ weyert
- chore(sdk-logs): refactored imports #5801 @ svetlanabrennan
- refactor(instrumentation-grpc): updated path to semconv #5884 @ overbalance
-
0.203.0 - 2025-07-09
- feat(sdk-logs)!: Removed deprecated LoggerProvider#addLogRecordProcessor() #5764 @ svetlanabrennan
- feat(sdk-logs)!: Changed
- user-facing:
- feat!: Removed
- chore: Regenerated certs #5752 @ svetlanabrennan
- refactor(otlp-exporter-base): remove compatibility code that was intended for now unsupported runtime Node.js v14 @ pichlermarc
from @opentelemetry/otlp-transformer GitHub release notes0.205.0
💥 Breaking Changes
createOtlpHttpExportDelegate(OtlpHttpConfiguration)has been changed to take a different, but identical typeOtlpNodeHttpConfigurationto differentiate it from the web-targeted exportersconvertLegacyHttpOptions(...)now returnsOtlpNodeHttpConfiguration, the returned object's contents remain identical.agentFactoryhas been dropped fromOtlpHttpConfigurationas it is node-specific and is now part ofOtlpNodeHttpConfigurationinstead0.204.0
💥 Breaking Changes
OtlpHttpConfiguration.agentOptionshas been removed and functionality has been rolled intoOtlpHttpConfiguration.agentFactory{ agentOptions: myOptions }{ agentFactory: httpAgentFactoryFromOptions(myOptions) }🚀 Features
fetchoverXMLHttpRequestif present. Sending viaXMLHttpRequestwill be removed in a future release.metricReadersoption in NodeSDK configuration. Users can now register multiple metric readers (e.g., Console, Prometheus) directly through the NodeSDK constructor. The oldmetricReader(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. #5760Migration:
Before:
After:
Users should migrate to the new
metricReadersarray option for future compatibility. The old option will be removed in an upcoming experimental version.🐛 Bug Fixes
esnextexport condition as it is more specific #5458🏠 Internal
0.203.0
💥 Breaking Changes
LogRecordclass to be an interface #5749 @ svetlanabrennanLogRecordclass is now not exported anymore. A newly exported interfaceSdkLogRecordis used in its place.api-eventsandsdk-events#5737 @ svetlanabrennan🏠 Internal
Important
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: