[Snyk] Upgrade @opentelemetry/sdk-node from 0.44.0 to 0.52.0

[moishimwe]

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.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 11 versions ahead of your current version.

• The recommended version was released on 25 days ago.

Release notes

Package name: @opentelemetry/sdk-node

• 0.52.0 - 2024-06-05
  

  0.52.0

  💥 Breaking Change

  • feat(exporter--otlp-)!: move serialization for Node.js exporters to @ opentelemetry/otlp-transformer #4542 @ pichlermarc
    • Breaking changes:
      • (user-facing) convert() now returns an empty object and will be removed in a follow-up
      • (internal) OTLPExporterNodeBase now has additional constructor parameters that are required
      • (internal) OTLPExporterNodeBase now has an additional ResponseType type parameter
  • feat(exporter--otlp-)!: move serialization for Node.js exporters to @ opentelemetry/otlp-transformer #4581 @ pichlermarc
    • Breaking changes:
      • (user-facing) convert() has been removed from all exporters
      • (internal) OTLPExporterBrowserBase: RequestType has been replaced by a ResponseType type-argument
      • (internal) OTLPExporterNodeBase: ServiceRequest has been replaced by a ServiceResponse type-argument
      • (internal) the @ opentelemetry/otlp-exporter-proto-base package has been removed, and will from now on be deprecated in npm
  • 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 registerInstrumentations() API
    • Breaking changes:
      • removes InstrumentationOptions type
      • occurrences of InstrumentationOptions are now replaced by (Instrumentation | Instrumentation[])[]
        • migrate usages of registerInstrumentations({instrumentations: fooInstrumentation}) to registerInstrumentations({instrumentations: [fooInstrumentation]})
        • passing Instrumentation classes to registerInstrumentations() is now not possible anymore.
  • feat(sdk-node)!: simplify type of instrumentations option
    • Breaking changes:
      • replaces InstrumentationOptions with (Instrumentation | Instrumentation[])[]

  🚀 (Enhancement)

  • 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

  🐛 (Bug Fix)

  • fix(instrumentation): Update import-in-the-middle to fix numerous bugs #4745 @ timfish

  📚 (Refine Doc)

  • 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
  

  0.51.1

  🐛 (Bug Fix)

  • fix(instrumentation): update import-in-the-middle to 1.7.4
• 0.51.0 - 2024-04-24
  

  0.51.0

  💥 Breaking Change

  • feat(sdk-node)!: remove long deprecated methods in favor of constructor options #4606 @ pichlermarc
    • NodeSDK.configureTracerProvider(), please use constructor options instead
    • NodeSDK.configureMeterProvider(), please use constructor options instead
    • NodeSDK.configureLoggerProvider(), please use constructor options instead
    • NodeSDK.addResource(), please use constructor options instead
    • NodeSDK.detectResources(), this is not necessary anymore, resources are now auto-detected on NodeSDK.start() if the constructor option autoDetectResources is unset, undefined or true.
  • 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
      • InstrumentationBase
      • InstrumentationNodeModuleDefinition
      • InstrumentationNodeModuleFile

  🚀 (Enhancement)

  • 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 serviceinstance to the list of resource detectors on the environment variable OTEL_NODE_RESOURCE_DETECTORS, e.g OTEL_NODE_RESOURCE_DETECTORS=env,host,os,serviceinstance
    • The value can be overwritten by
      • merging a resource containing the service.instance.id attribute
      • using another resource detector which writes service.instance.id

  🐛 (Bug Fix)

  • fix(otlp-grpc-exporter-base): avoid TypeError on exporter shutdown #4612 @ pichlermarc
  • fix(instrumentation): Don't use require to load package.json files #4593 @ timfish
• 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 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:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs