Bump semantic_conventions gem to 1.10.0 #1171
Merged
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
I couldn't find any huge changes from the release notes; it seems the generated wording was improved in some cases. Regardless, let us not drift too far behind.
The most notable thing here is that the delta between 1.8.0 and 1.10.0 results in a few fields going away. This will be a breaking change for anyone who happens to be depending upon these fields: - `DB_CASSANDRA_KEYSPACE` - `DB_HBASE_NAMESPACE` Users should instead use `DB_NAME`, according to [open-telemetry/opentelemetry-specification#1973](open-telemetry/opentelemetry-specification#1973). Otherwise, we get the standard deal: - A plethora of new, exciting fields! - Reworded explanatory text! Overall, not a terribly exciting change, but we must often take joy in the small things, and I choose to do so here!
ahayworth
requested review from
fbogsany,
mwear,
robertlaurin,
dazuma,
ericmustin and
arielvalentin
as code owners
plantfansam
approved these changes
Apr 7, 2022
fbogsany
approved these changes
Apr 8, 2022
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.
This PR bumps the semantic_conventions gem to the 1.10.0 semantic conventions release.
It's fairly uninteresting overall; but the commit messages have the full details and are replayed here for your convenience.
feat!: update for semantic conventions @ v1.10.0
The most notable thing here is that the delta between 1.8.0 and 1.10.0
results in a few fields going away. This will be a breaking change for
anyone who happens to be depending upon these fields:
DB_CASSANDRA_KEYSPACEDB_HBASE_NAMESPACEUsers should instead use
DB_NAME, according toopen-telemetry/opentelemetry-specification#1973.
Otherwise, we get the standard deal:
Overall, not a terribly exciting change, but we must often take joy in
the small things, and I choose to do so here!
chore: bump semconvgen from 0.4.1 -> 0.11.1
I couldn't find any huge changes from the release notes; it seems the
generated wording was improved in some cases. Regardless, let us not
drift too far behind.