[Snyk] Upgrade @opentelemetry/context-zone from 2.6.0 to 2.6.1#3209
Closed
[Snyk] Upgrade @opentelemetry/context-zone from 2.6.0 to 2.6.1#3209
Conversation
Snyk has created this PR to upgrade @opentelemetry/context-zone from 2.6.0 to 2.6.1. See this package in npm: @opentelemetry/context-zone See this project in Snyk: https://app.snyk.io/org/docs-wmk/project/69782e43-c85b-4c27-afd1-ad863be7a38a?utm_source=github&utm_medium=referral&page=upgrade-pr
Contributor
Author
|
This is a patch version upgrade that includes a bug fix for the Change Details:
This change is a targeted bug fix and does not introduce any breaking API changes. Source: OpenTelemetry-JS Changelog
|
Contributor
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade @opentelemetry/context-zone from 2.6.0 to 2.6.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 1 version ahead of your current version.
The recommended version was released a month ago.
Issues fixed by the recommended upgrade:
SNYK-JS-PROTOBUFJS-16094665
SNYK-JS-PROTOBUFJS-16094665
Breaking Change Risk
Release notes
Package name: @opentelemetry/context-zone
-
2.6.1 - 2026-03-25
- fix(opentelemetry-instrumentation): improve
- fix(sdk-trace-base): derive internal
- fix(span): enforce
- chore: enforce
- perf(sdk-trace-base): avoid Object.entries in Span.setAttributes #6514 @ daniellockyer
- perf(sdk-trace-base): optimize
- test(bundlers): broaden bundler test coverage and assert known protobuf dynamic-require failures #6482 @ overbalance
-
2.6.0 - 2026-03-03
- fix(resources): update
- Important: This fix is included in the "breaking changes" section because it can be breaking for some edge case usage of
- feat(sdk-trace): implement span start/end metrics #6213 @ anuraaga
- fix(sdk-trace-web): propagate
from @opentelemetry/context-zone GitHub release notes2.6.1
🐛 Bug Fixes
_warnOnPreloadedModulesfunction not to show warning logs when the module is not marked as loaded #6095 @ rlj1202SpanOptionsfrom API type to prevent drift #6478 @ overbalanceattributePerEventCountLimit,attributePerLinkCountLimit,linkCountLimit, andattributeValueLengthLimitfor event/link attributes #6479 @ overbalance🏠 Internal
import typefor type-only imports via ESLint #6467 @ overbalanceSpan.{addEvent,addLink}performance #6516 @ daniellockyer2.6.0
💥 Breaking Changes
OTEL_RESOURCE_ATTRIBUTESparsing to match spec changes (open-telemetry/opentelemetry-specification#4856) #6261 @ JacksonWeberOTEL_RESOURCE_ATTRIBUTES:export OTEL_RESOURCE_ATTRIBUTES=foo=bar,spamwill now be fully ignored, because thespamentry is invalid (missing=). Per spec, any parsing error results in ignoring the entire environment variable.export OTEL_RESOURCE_ATTRIBUTES='wat=" spaces "'will now result in{"wat": "\" spaces \""}with the double-quotes included in the value. Before this change the implementation included brittle double-quoting to allow leading and trailing whitespace in the value. To support leading or trailing whitespace now, you must percent-encode the whitespace. Internal whitespace still works without encoding, e.g.export OTEL_RESOURCE_ATTRIBUTES='green=eggs and ham'.🚀 Features
🐛 Bug Fixes
optimisedflag ingetElementXPathrecursion #6335 @ akkupratap323Important
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: