Skip to content

Conversation

@hashim21223445
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade @opentelemetry/exporter-trace-otlp-http from 0.51.1 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 2 versions ahead of your current version.

  • The recommended version was released on a month ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Uncontrolled resource consumption
SNYK-JS-BRACES-6838727
169 Proof of Concept
high severity Inefficient Regular Expression Complexity
SNYK-JS-MICROMATCH-6838728
169 No Known Exploit
medium severity Uncontrolled Resource Consumption
SNYK-JS-GRPCGRPCJS-7242922
169 No Known Exploit
Release notes
Package name: @opentelemetry/exporter-trace-otlp-http
  • 0.52.1 - 2024-06-20

    0.52.1

    🚀 (Enhancement)

    • refactor(instrumentation-fetch): move fetch to use SEMATRR #4632
    • refactor(otlp-transformer): use explicit exports #4785 @ pichlermarc

    🐛 (Bug Fix)

    🏠 (Internal)

    • test: add npm run maint:regenerate-test-certs maintenance script and regenerate recently expired test certs #4777
  • 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)

    📚 (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
from @opentelemetry/exporter-trace-otlp-http 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.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

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:

….52.1

Snyk has created this PR to upgrade @opentelemetry/exporter-trace-otlp-http from 0.51.1 to 0.52.1.

See this package in npm:
@opentelemetry/exporter-trace-otlp-http

See this project in Snyk:
https://app.snyk.io/org/hashim21223445/project/1cbe4b58-3b34-4dde-844d-8068d16123e6?utm_source=github&utm_medium=referral&page=upgrade-pr
@hashim21223445 hashim21223445 self-assigned this Jan 23, 2025
@hashim21223445 hashim21223445 added this to the Faire une demande milestone Jan 23, 2025
@hashim21223445 hashim21223445 added merge when passing Merge the PR automatically once all status checks have passed patch version Automatically create a new patch version tag after PR is merged minor version Automatically create a new minor version tag after PR is merged major version Automatically create a new major version tag after PR is merged dependencies Pull requests that update a dependency file labels Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file major version Automatically create a new major version tag after PR is merged merge when passing Merge the PR automatically once all status checks have passed minor version Automatically create a new minor version tag after PR is merged patch version Automatically create a new patch version tag after PR is merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants