Skip to content
New issue

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

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

Already on GitHub? # to your account

[Snyk] Upgrade @opentelemetry/context-zone from 1.25.1 to 1.26.0 #2

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

Conversation

rreckless
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade @opentelemetry/context-zone from 1.25.1 to 1.26.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 1 version ahead of your current version.

  • The recommended version was released on a month ago.

Release notes
Package name: @opentelemetry/context-zone
  • 1.26.0 - 2024-08-28

    1.26.0

    🚀 (Enhancement)

    • feat: include instrumentation scope info in console span and log record exporters #4848 @ blumamir
    • feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690 @ dyladan
      • Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
      • Import @ opentelemetry/semantic-conventions for stable semantic conventions. Import @ opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
      • Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.

    🐛 (Bug Fix)

    • fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879 @ trentm
    • deps(opentelemetry-instrumentation): Bump shimmer types to 1.2.0 #4865 @ lforst
    • fix(instrumentation): Fix optional property types #4833 @ alecmev
    • fix(sdk-metrics): fix(sdk-metrics): use inclusive upper bounds in histogram #4829

    🏠 (Internal)

    • refactor: Simplify the code for the getEnv function #4799 @ danstarns
    • refactor: remove "export *" in favor of explicit named exports #4880 @ robbkidd
      • Packages updated:
        • opentelemetry-context-zone
        • opentelemetry-core
        • opentelemetry-exporter-jaeger
        • opentelemetry-exporter-zipkin
        • opentelemetry-propagator-b3
        • opentelemetry-propagator-jaeger
        • opentelemetry-sdk-trace-base
        • opentelemetry-sdk-trace-node
        • opentelemetry-sdk-trace-web
        • propagator-aws-xray
        • sdk-metrics
    • deps(sdk-metrics): remove unused lodash.merge dependency #4905 @ pichlermarc
  • 1.25.1 - 2024-06-20

    1.25.1

    📚 (Refine Doc)

    • refactor(examples): added usage of @ opentelemetry/semantic-conventions and @ opentelemetry/resources to the examples in examples/opentelemetry-web for maintaining consistency across all examples. #4764 @ Zen-cronic

    🏠 (Internal)

from @opentelemetry/context-zone 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:

Snyk has created this PR to upgrade @opentelemetry/context-zone from 1.25.1 to 1.26.0.

See this package in npm:
@opentelemetry/context-zone

See this project in Snyk:
https://app.snyk.io/org/rob.reckless/project/4c81294e-9a8f-4394-98f1-19bcbad808c2?utm_source=github&utm_medium=referral&page=upgrade-pr
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants