[Snyk] Upgrade @opentelemetry/instrumentation from 0.53.0 to 0.203.0 #36
Conversation
This file contains hidden or 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.203.0. See this package in npm: @opentelemetry/instrumentation See this project in Snyk: https://app.snyk.io/org/snapp949/project/adcad846-d2e2-485a-9523-e301cbb0e4cc?utm_source=github&utm_medium=referral&page=upgrade-pr
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.203.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 16 versions ahead of your current version.
The recommended version was released a month ago.
Release notes
Package name: @opentelemetry/instrumentation
-
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
-
0.202.0 - 2025-06-02
- feat(exporter-otlp-*): update proto to
- feat(exporter-metrics-otlp-proto): Support to protobuf in browser metrics. #5710 @ YangJonghun
- fix(instrumentation): remove dependency on the shimmer module #5652 @ cjihrig
-
0.201.1 - 2025-05-19
- fix(instrumentation): Change
-
0.201.0 - 2025-05-15
- feat(instrumentation-xml-http-request): support migration to stable HTTP semconv, v1.23.1 #5662 @ trentm
- Configure the instrumentation with
- feat(instrumentation-fetch): support migration to stable HTTP semconv, v1.23.1 #5651 @ trentm
- Configure the instrumentation with
- feat(instrumentation): New
- See the utility comment.
- feat(instrumentation-grpc): support migration to stable HTTP semconv #5653 @ JamieDanielson
- feat(instrumentation-http): capture synthetic source type on requests #5488 @ JacksonWeber
- fix(otlp-transformer): do not throw when deserializing empty JSON response #5551 @ pichlermarc
- fix(instrumentation-http): report stable client metrics response code #9586 @ jtescher
- fix(sdk-node): instantiate baggage processor when env var is set #5634 @ pichlermarc
- refactor(instrumentation-http): Remove legacy http span attributes and metrics #5552 @ svetlanabrennan
- refactor(instrumentation-http): Add back support for http semconv #5665 @ JamieDanielson
- Note: We initially removed support for legacy http attributes and metrics, but then added back for an additional 6 months to ensure all instrumentations could be updated and kept consistent. There should be no net new change in this instrumentation related to these semantic conventions. See #5646 for details.
- refactor(sdk-node): update semconv usage to
- chore(sdk-node): Refactored using
- chore(sdk-node): Refactored using
- test: test Node.js 24 in CI #5661 @ cjihrig
-
0.200.0 - 2025-03-17
-
0.200.0-rc.1 - 2025-03-12
-
0.200.0-dev.1 - 2025-03-05
-
0.200.0-dev.0 - 2025-02-24
-
0.57.2 - 2025-02-13
-
0.57.1 - 2025-01-14
-
0.57.0 - 2024-12-18
-
0.56.0 - 2024-12-04
-
0.55.0 - 2024-11-18
-
0.54.2 - 2024-11-07
-
0.54.1 - 2024-11-05
-
0.54.0 - 2024-10-23
-
0.53.0 - 2024-08-28
from @opentelemetry/instrumentation GitHub release notes0.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
0.202.0
🚀 Features
v1.7.0🐛 Bug Fixes
0.201.1
🐛 Bug Fixes
SemconvStabilityexport fromconst enumtoenumto allow single-file transpilation tooling to work with code that usesSemconvStability. #5691 @ trentm0.201.0
🚀 Features
semconvStabilityOptIn: 'http'to use the new, stable semconv v1.23.1 semantics or'http/dup'for both old (v1.7.0) and stable semantics. WhensemconvStabilityOptInis not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.semconvStabilityOptIn: 'http'to use the new, stable semconv v1.23.1 semantics or'http/dup'for both old (v1.7.0) and stable semantics. WhensemconvStabilityOptInis not specified (or does not contain these values), it uses the old semconv v1.7.0. I.e. the default behavior is unchanged.semconvStabilityFromStr()utility for semconv stability migration in instrumentations. #5684 @ trentm🐛 Bug Fixes
🏠 Internal
ATTR_exports #5668 @ trentmget*FromEnvutility function instead ofprocess.envfor NodeSDK's resource detector setup. #5582 @ beeme1mrget*FromEnvutility function instead ofprocess.envfor NodeSDK's logging setup. #5563 @ weyertImportant
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: