[Snyk] Upgrade @opentelemetry/semantic-conventions from 1.7.0 to 1.22.0 #428
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.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade @opentelemetry/semantic-conventions from 1.7.0 to 1.22.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.
Release notes
Package name: @opentelemetry/semantic-conventions
1.22.0
🚀 (Enhancement)
🐛 (Bug Fix)
NaN
value recordings in Histograms #4455 @ pichlermarcNaN
on a histogram would result in the sum of bucket count values not matching the overall countMeter.createHistogram()
with the adviceexplicitBucketBoundaries: []
would throwzone.js
affected by angular/angular#53507 would be pulled in📚 (Refine Doc)
1.21.0
🚀 (Enhancement)
MeterProvider.addMetricReader()
please use the constructor optionreaders
instead.🐛 (Bug Fix)
🏠 (Internal)
1.20.0
🚀 (Enhancement)
🚀 (Enhancement)
🏠 (Internal)
🐛 (Bug Fix)
API v1.8.0
🚀 (Enhancement)
🐛 (Bug Fix)
Commit messages
Package name: @opentelemetry/semantic-conventions
Compare
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:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs