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: , , , , , , , #61

Merged
merged 1 commit into from
Sep 22, 2024

Conversation

zx8086
Copy link
Owner

@zx8086 zx8086 commented Sep 19, 2024

snyk-top-banner

Snyk has created this PR to upgrade multiple dependencies.

👯‍♂ The following dependencies are linked and will therefore be updated together.

ℹ️ 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.

Name Versions Released on

@opentelemetry/instrumentation-http
from 0.52.1 to 0.53.0 | 1 version ahead of your current version | 22 days ago
on 2024-08-28
@opentelemetry/sdk-logs
from 0.52.1 to 0.53.0 | 1 version ahead of your current version | 22 days ago
on 2024-08-28
@opentelemetry/exporter-trace-otlp-http
from 0.52.1 to 0.53.0 | 1 version ahead of your current version | 22 days ago
on 2024-08-28
@opentelemetry/sdk-node
from 0.52.1 to 0.53.0 | 1 version ahead of your current version | 22 days ago
on 2024-08-28
@opentelemetry/exporter-logs-otlp-http
from 0.52.1 to 0.53.0 | 1 version ahead of your current version | 22 days ago
on 2024-08-28
@opentelemetry/exporter-metrics-otlp-http
from 0.52.1 to 0.53.0 | 1 version ahead of your current version | 22 days ago
on 2024-08-28
@opentelemetry/instrumentation-fetch
from 0.52.1 to 0.53.0 | 1 version ahead of your current version | 22 days ago
on 2024-08-28
@opentelemetry/instrumentation-xml-http-request
from 0.52.1 to 0.53.0 | 1 version ahead of your current version | 22 days ago
on 2024-08-28

Release notes
Package name: @opentelemetry/instrumentation-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
from @opentelemetry/instrumentation-http GitHub release notes
Package name: @opentelemetry/sdk-logs
  • 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
from @opentelemetry/sdk-logs GitHub 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
from @opentelemetry/exporter-trace-otlp-http GitHub release notes
Package name: @opentelemetry/sdk-node
  • 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
from @opentelemetry/sdk-node GitHub release notes
Package name: @opentelemetry/exporter-logs-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
from @opentelemetry/exporter-logs-otlp-http GitHub release notes
Package name: @opentelemetry/exporter-metrics-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

Snyk has created this PR to upgrade:
  - @opentelemetry/instrumentation-http from 0.52.1 to 0.53.0.
    See this package in npm: https://www.npmjs.com/package/@opentelemetry/instrumentation-http
  - @opentelemetry/sdk-logs from 0.52.1 to 0.53.0.
    See this package in npm: https://www.npmjs.com/package/@opentelemetry/sdk-logs
  - @opentelemetry/exporter-trace-otlp-http from 0.52.1 to 0.53.0.
    See this package in npm: https://www.npmjs.com/package/@opentelemetry/exporter-trace-otlp-http
  - @opentelemetry/sdk-node from 0.52.1 to 0.53.0.
    See this package in npm: https://www.npmjs.com/package/@opentelemetry/sdk-node
  - @opentelemetry/exporter-logs-otlp-http from 0.52.1 to 0.53.0.
    See this package in npm: https://www.npmjs.com/package/@opentelemetry/exporter-logs-otlp-http
  - @opentelemetry/exporter-metrics-otlp-http from 0.52.1 to 0.53.0.
    See this package in npm: https://www.npmjs.com/package/@opentelemetry/exporter-metrics-otlp-http
  - @opentelemetry/instrumentation-fetch from 0.52.1 to 0.53.0.
    See this package in npm: https://www.npmjs.com/package/@opentelemetry/instrumentation-fetch
  - @opentelemetry/instrumentation-xml-http-request from 0.52.1 to 0.53.0.
    See this package in npm: https://www.npmjs.com/package/@opentelemetry/instrumentation-xml-http-request

See this project in Snyk:
https://app.snyk.io/org/zx8086/project/5ed51654-f59c-4dfe-b23a-8b2a68aa9a2e?utm_source=github&utm_medium=referral&page=upgrade-pr
@zx8086 zx8086 closed this Sep 22, 2024
@zx8086 zx8086 reopened this Sep 22, 2024
@zx8086 zx8086 merged commit 7089e7e into master Sep 22, 2024
1 check passed
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