[Snyk] Upgrade @opentelemetry/sdk-node from 0.44.0 to 0.52.1 #3
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.
This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade @opentelemetry/sdk-node from 0.44.0 to 0.52.1.
ℹ️ 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 12 versions ahead of your current version.
The recommended version was released on a month ago.
Release notes
Package name: @opentelemetry/sdk-node
-
0.52.1 - 2024-06-20
- refactor(instrumentation-fetch): move fetch to use SEMATRR #4632
- refactor(otlp-transformer): use explicit exports #4785 @ pichlermarc
- fix(sdk-node): register context manager if no tracer options are provided #4781 @ pichlermarc
- fix(instrumentation): Update
- chore(instrumentation): Use a caret version for
- test: add
-
0.52.0 - 2024-06-05
- feat(exporter--otlp-)!: move serialization for Node.js exporters to
- Breaking changes:
- (user-facing)
- (internal) OTLPExporterNodeBase now has additional constructor parameters that are required
- (internal) OTLPExporterNodeBase now has an additional
- feat(exporter--otlp-)!: move serialization for Node.js exporters to
- Breaking changes:
- (user-facing)
- (internal) OTLPExporterBrowserBase:
- (internal) OTLPExporterNodeBase:
- (internal) the
- feat(instrumentation): remove default value for config in base instrumentation constructor #4695: @ blumamir
- fix(instrumentation)!: remove unused supportedVersions from Instrumentation interface #4694 @ blumamir
- feat(instrumentation)!: simplify
- Breaking changes:
- removes
- occurrences of
- migrate usages of
- passing Instrumentation classes to
- feat(sdk-node)!: simplify type of
- Breaking changes:
- replaces
- feat(instrumentation): apply unwrap before wrap in base class #4692
- feat(instrumentation): add util to execute span customization hook in base class #4663 @ blumamir
- feat(instrumentation): generic config type in instrumentation base #4659 @ blumamir
- feat: support node 22 #4666 @ dyladan
- feat(propagator-aws-xray-lambda): add AWS Xray Lambda propagator 4554
- refactor(instrumentation-xml-http-request): use exported strings for semantic attributes. #4681
- fix(instrumentation): Update
- docs(instrumentation): better docs for supportedVersions option #4693 @ blumamir
- docs: align all supported versions to a common format #4696 @ blumamir
- refactor(examples): use new exported string constants for semconv in experimental/examples/opencensus-shim #4763 @ Zen-cronic
-
0.51.1 - 2024-05-07
- fix(instrumentation): update import-in-the-middle to 1.7.4
-
0.51.0 - 2024-04-24
- feat(sdk-node)!: remove long deprecated methods in favor of constructor options #4606 @ pichlermarc
- feat(instrumentation): add patch and unpatch diag log messages #4641
- Instrumentations should not log patch and unpatch messages to diag channel.
- feat!(instrumentation): remove moduleExports generic type from instrumentation registration #4598 @ blumamir
- breaking for instrumentation authors that depend on
- refactor(instrumentation-grpc): move to use SEMATTRS #4633
- feat(otlp-transformer): consolidate scope/resource creation in transformer #4600
- feat(sdk-logs): print message when attributes are dropped due to attribute count limit #4614 @ HyunnoH
- feat(sdk-node): add usage for the detector ServiceInstanceIdDetectorSync. #4626 @ maryliag
- The resource detector can be added to default resource detector list by adding the value
- The value can be overwritten by
- merging a resource containing the
- using another resource detector which writes
- fix(otlp-grpc-exporter-base): avoid TypeError on exporter shutdown #4612 @ pichlermarc
- fix(instrumentation): Don't use
-
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
from @opentelemetry/sdk-node GitHub release notes0.52.1
🚀 (Enhancement)
🐛 (Bug Fix)
import-in-the-middleto fix numerous bugs #4806 @ timfishimport-in-the-middledependency #4810 @ timfish🏠 (Internal)
npm run maint:regenerate-test-certsmaintenance script and regenerate recently expired test certs #47770.52.0
💥 Breaking Change
@ opentelemetry/otlp-transformer#4542 @ pichlermarcconvert()now returns an empty object and will be removed in a follow-upResponseTypetype parameter@ opentelemetry/otlp-transformer#4581 @ pichlermarcconvert()has been removed from all exportersRequestTypehas been replaced by aResponseTypetype-argumentServiceRequesthas been replaced by aServiceResponsetype-argument@ opentelemetry/otlp-exporter-proto-basepackage has been removed, and will from now on be deprecated innpmregisterInstrumentations()APIInstrumentationOptionstypeInstrumentationOptionsare now replaced by(Instrumentation | Instrumentation[])[]registerInstrumentations({instrumentations: fooInstrumentation})toregisterInstrumentations({instrumentations: [fooInstrumentation]})registerInstrumentations()is now not possible anymore.instrumentationsoptionInstrumentationOptionswith(Instrumentation | Instrumentation[])[]🚀 (Enhancement)
🐛 (Bug Fix)
import-in-the-middleto fix numerous bugs #4745 @ timfish📚 (Refine Doc)
0.51.1
🐛 (Bug Fix)
0.51.0
💥 Breaking Change
NodeSDK.configureTracerProvider(), please use constructor options insteadNodeSDK.configureMeterProvider(), please use constructor options insteadNodeSDK.configureLoggerProvider(), please use constructor options insteadNodeSDK.addResource(), please use constructor options insteadNodeSDK.detectResources(), this is not necessary anymore, resources are now auto-detected onNodeSDK.start()if the constructor optionautoDetectResourcesis unset,undefinedortrue.InstrumentationBaseInstrumentationNodeModuleDefinitionInstrumentationNodeModuleFile🚀 (Enhancement)
serviceinstanceto the list of resource detectors on the environment variableOTEL_NODE_RESOURCE_DETECTORS, e.gOTEL_NODE_RESOURCE_DETECTORS=env,host,os,serviceinstanceservice.instance.idattributeservice.instance.id🐛 (Bug Fix)
requireto loadpackage.jsonfiles #4593 @ timfishImportant
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: