feat: upgrade semantic conventions to the latest 1.6.1 version #2456
Conversation
This file contains 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
Regenerated the `@opentelemetry-js/semantic-conventions`-package to use the latest definitions from the Opentelemetry specification
Codecov Report
@@ Coverage Diff @@
## main #2456 +/- ##
=======================================
Coverage 92.56% 92.56%
=======================================
Files 134 134
Lines 4871 4871
Branches 1036 1036
=======================================
Hits 4509 4509
Misses 362 362 |
vmarchaud
approved these changes
Sep 4, 2021
naseemkullah
approved these changes
Sep 5, 2021
rauno56
approved these changes
Sep 6, 2021
This was referenced May 26, 2023
[Snyk] Upgrade @opentelemetry/exporter-jaeger from 0.25.0 to 0.26.0
0xETHengineer/opentelemetry-js#2
Open
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.
Regenerated the
@opentelemetry-js/semantic-conventions-package to usethe latest definitions from the Opentelemetry specification
Which problem is this PR solving?
Short description of the changes