[Snyk] Upgrade @opentelemetry/instrumentation from 0.53.0 to 0.54.2 #165
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade @opentelemetry/instrumentation from 0.53.0 to 0.54.2. See this package in npm: @opentelemetry/instrumentation See this project in Snyk: https://app.snyk.io/org/womb0comb0/project/50c3f21a-4385-405f-99d6-387977cfff55?utm_source=github&utm_medium=referral&page=upgrade-pr
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
🎉 This PR is included in version 1.0.6 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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/instrumentation from 0.53.0 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 3 versions ahead of your current version.
The recommended version was released on 22 days ago.
Release notes
Package name: @opentelemetry/instrumentation
-
0.54.2 - 2024-11-07
- fix(instrumentation): Fix wrapping ESM files with absolute path #5094 @ serkan-ozal
-
0.54.1 - 2024-11-05
- fix(instrumentation-http): skip malformed forwarded headers. #5095 @ pmlanger
-
0.54.0 - 2024-10-23
- feat(exporter--otlp-)!: rewrite exporter config logic for testability #4971 @ pichlermarc
- (user-facing)
- (user-facing)
- (user-facing)
- (user-facing)
- (user-facing)
- (user-facing)
- (user-facing) OTLP exporter config
- 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:
- feat(instrumentation-http)!: remove long deprecated options #5085 @ pichlermarc
- 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
- Generate spans and metrics backwards compatible with previous attributes when
- fix(sampler-jaeger-remote): fixes an issue where package could emit unhandled promise rejections @ Just-Sieb
- fix(otlp-grpc-exporter-base): default compression to
- fix(sdk-events): remove devDependencies to old
- fix(sdk-logs): remove devDependencies to old
- fix(sdk-logs): align LogRecord#setAttribute type with types from
- 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:
- 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
-
-
-
-
0.53.0 - 2024-08-28
- fix(instrumentation)!:remove unused description property from interface #4847 @ blumamir
- feat(exporter--otlp-)!: use transport interface in node.js exporters #4743 @ pichlermarc
- (user-facing)
- (user-facing)
- (user-facing)
- fix(exporter--otlp-)!: ensure
- allowing overrides of the
- feat(exporter--otlp)!: remove environment-variable specific code from browser exporters
- (user-facing) removes the ability to configure browser exporters by using
- feat(sdk-node)!: Automatically configure logs exporter #4740
- feat(exporter--otlp-)!: use transport interface in browser exporters #4895 @ pichlermarc
- (user-facing) protected
- feat(otlp-transformer): Do not limit @ opentelemetry/api upper range peerDependency #4816 @ mydea
- feat(instrumentation-http): Allow to opt-out of instrumenting incoming/outgoing requests #4643 @ mydea
- feat(sampler-jaeger-remote): added support of jaeger-remote-sampler according to this spec #4534 @ legalimpurity
- fix(instrumentation): ensure .setConfig() results in config.enabled defaulting to true #4941 @ trentm
- fix(instrumentation-http): Ensure instrumentation of
- fix(api-logs): align AnyValue to spec #4893 @ blumamir
- fix(instrumentation): remove diag.debug() message for instrumentations that do not patch modules #4925 @ trentm
- refactor: Simplify the code for the
- refactor: remove "export *" in favor of explicit named exports #4880 @ robbkidd
- Packages updated:
- api-events
- api-logs
- opentelemetry-browser-detector
- opentelemetry-exporter-prometheus
- opentelemetry-instrumentation-fetch
- opentelemetry-instrumentation-http
- opentelemetry-instrumentation-xml-http-request
- opentelemetry-instrumentation
from @opentelemetry/instrumentation GitHub release notes0.54.2
🐛 (Bug Fix)
0.54.1
🐛 (Bug Fix)
0.54.0
💥 Breaking Change
getDefaultUrlwas intended for internal use has been removed from all exportersgetUrlFromConfigwas intended for internal use and has been removed from all exportershostnamewas intended for internal use and has been removed from all exportersurlwas intended for internal use and has been removed from all exporterstimeoutMilliswas intended for internal use and has been removed from all exportersonInitwas intended for internal use and has been removed from all exportersheaderstype changed fromPartial<Record<string, unknown>>toRecord<string, string>parseHeadersappendResourcePathToUrlappendResourcePathToUrlIfNeededconfigureExporterTimeoutinvalidTimeoutignoreIncomingPathshas been removed, use the more versatileignoreIncomingRequestHookinstead.ignoreOutgoingUrlshas been removed, use the more versatileignoreOutgoingRequestHookinstead.isIgnoredutility function was intended for internal use and has been removed without replacement.🚀 (Enhancement)
OTEL_SEMCONV_STABILITY_OPT_INcontainshttporhttp/dupOTEL_SEMCONV_STABILITY_OPT_INcontainshttp/dupor DOES NOT containhttp🐛 (Bug Fix)
'none'if env varsOTEL_EXPORTER_OTLP_TRACES_COMPRESSIONandOTEL_EXPORTER_OTLP_COMPRESSIONare falsy @ sjvans@ opentelemetry/api-logs@0.52.0,@ opentelemetry/api-events@0.52.0packages #5013 @ pichlermarc@ opentelemetry/api-logs@0.52.0#5013 @ pichlermarc@ opentelemetry/api-logs@0.53.0#5013 @ pichlermarcOTEL_EXPORTER_OTLP_METRICS_COMPRESSIONOTEL_EXPORTER_OTLP_LOGS_COMPRESSIONOTEL_EXPORTER_OTLP_METRICS_CLIENT_CERTIFICATEOTEL_EXPORTER_OTLP_LOGS_CLIENT_CERTIFICATEOTEL_EXPORTER_OTLP_METRICS_CLIENT_KEYOTEL_EXPORTER_OTLP_LOGS_CLIENT_KEYOTEL_EXPORTER_OTLP_METRICS_INSECUREOTEL_EXPORTER_OTLP_LOGS_INSECUREhttp.get,http.request,https.get, andhttps.requestwhen used from ESM code and imported via theimport defaultExport from 'http'style. #5024 @ trentm🏠 (Internal)
refactor(exporter-prometheus): replace
MetricAttributesandMetricAttributeValueswithAttributesandAttributeValues#4993refactor(browser-detector): replace
ResourceAttributeswithAttributes#5004refactor(sdk-logs): replace
ResourceAttributeswithAttributes#5005 @ david-luna0.53.0
💥 Breaking Change
headerswas intended for internal use has been removed from all exporterscompressionwas intended for internal use and has been removed from all exportershostnamewas intended for use in tests and is not used by any exporters, it will be removed in a future releaseUser-Agentheader cannot be overwritten by the user #4743 @ pichlermarcUser-Agentheader was not specification compliant.process.envpolyfillsheadersproperty was intended for internal use has been removed from all exporters🚀 (Enhancement)
🐛 (Bug Fix)
http.getandhttps.getwork when used in ESM code #4857 @ trentm🏠 (Internal)
getEnvfunction #4799 @ danstarnsImportant
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: