Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade @opentelemetry/exporter-trace-otlp-http from 0.41.2 to 0.53.0 #43

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

WontonSam
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade @opentelemetry/exporter-trace-otlp-http from 0.41.2 to 0.53.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 on a month ago.

Release notes
Package name: @opentelemetry/exporter-trace-otlp-http
  • 0.53.0 - 2024-08-28

    0.53.0

    💥 Breaking Change

    • fix(instrumentation)!:remove unused description property from interface #4847 @ blumamir
    • feat(exporter--otlp-)!: use transport interface in node.js exporters #4743 @ pichlermarc
      • (user-facing) headers was intended for internal use has been removed from all exporters
      • (user-facing) compression was intended for internal use and has been removed from all exporters
      • (user-facing) hostname was intended for use in tests and is not used by any exporters, it will be removed in a future release
    • fix(exporter--otlp-)!: ensure User-Agent header cannot be overwritten by the user #4743 @ pichlermarc
      • allowing overrides of the User-Agent header was not specification compliant.
    • feat(exporter--otlp)!: remove environment-variable specific code from browser exporters
      • (user-facing) removes the ability to configure browser exporters by using process.env polyfills
    • feat(sdk-node)!: Automatically configure logs exporter #4740
    • feat(exporter--otlp-)!: use transport interface in browser exporters #4895 @ pichlermarc
      • (user-facing) protected headers property was intended for internal use has been removed from all exporters

    🚀 (Enhancement)

    • 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

    🐛 (Bug Fix)

    • fix(instrumentation): ensure .setConfig() results in config.enabled defaulting to true #4941 @ trentm
    • fix(instrumentation-http): Ensure instrumentation of http.get and https.get work when used in ESM code #4857 @ trentm
    • fix(api-logs): align AnyValue to spec #4893 @ blumamir
    • fix(instrumentation): remove diag.debug() message for instrumentations that do not patch modules #4925 @ trentm

    🏠 (Internal)

    • refactor: Simplify the code for the getEnv function #4799 @ danstarns
    • 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
  • 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.0 - 2024-04-24
  • 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
  • 0.43.0 - 2023-09-12
  • 0.42.0 - 2023-09-11
  • 0.41.2 - 2023-08-08
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.

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:

….53.0

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

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

See this project in Snyk:
https://app.snyk.io/org/cachiman-inc/project/060a5e2e-dc2c-4423-8894-4c35bba65e8b?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

google-cla bot commented Sep 27, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants