opentelemetry-semantic_conventions 1.10.0 → 1.37.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c6700592df6568f5f7b0bae5e9d3443439c2562a9d023a1ce3d154ac8f752707
-  data.tar.gz: 8d4b43b6f27fe6052ef8fd066d48bdf7bd42bf444c68b4cdb29f974f89ce2496
+  metadata.gz: ae5e00b9714aa7b343b498aa617582048e0713aa12ed975d0c4ef9350ce8532e
+  data.tar.gz: 5e8c4e48bda8d05d69652457fd07d11497d154acb603dbb876aa16b697108d7d
 SHA512:
-  metadata.gz: 1dfab8f7100ff3ec062b66b4c1ba09e5f2ff3c445c74c805c9d259bce857c7c78a104f46c6447bbb973bd64ebea53bfdfba7c5e4f5bcb4772e57f9a2f813d691
-  data.tar.gz: e34cb3bff877719f7d19a6af066bd66322f5b86db703e3caded156992dccdf9d253bfd0fe59c5e4353ede6ba2ab6e5203c63736e60ee474ac7b6697f2505fc91
+  metadata.gz: cf7612172fe08e1fc05445a50d3abb8e3911946a2b1fc97098c787baa9b7e3e16bf08b5239d392c2eec45fc6af12931a590a5d4e98ba609d42fcfa050002855f
+  data.tar.gz: d399cbaaf4cad564fe862bc7e2fce0cf6dbfd9be628c4175b6e1cd336a4164b6a9ab08f164746975d411f762198c777a6e8162ff61361079ff6985a9423252d6

data/.yardopts

@@ -1,9 +1,9 @@
 --no-private
 --title=OpenTelemetry Semantic Conventions
 --markup=markdown
+--markup-provider=kramdown
 --main=README.md
-./lib/opentelemetry/semantic_conventions/**/*.rb
-./lib/opentelemetry/semantic_conventions.rb
+./lib/opentelemetry/**/*.rb
 -
 README.md
 CHANGELOG.md

data/CHANGELOG.md

@@ -1,24 +1,45 @@
 # Release History: opentelemetry-semantic_conventions
 
+### v1.37.0 / 2026-04-07
+
+* ADDED: Bump semantic conventions to version 1.37.0 (#1952)
+* ADDED: Min Ruby Version 3.3 (#2070)
+* FIXED: Correct & simplify codegen templates (#2059)
+* FIXED: Tweak weaver generation to include new line (#2071)
+
+### v1.36.0 / 2025-09-16
+
+* ADDED: Update to v1.36 in a non-breaking way
+
+### v1.11.0 / 2025-02-25
+
+- ADDED: Support 3.1 Min Version
+
+### v1.10.1 / 2024-07-24
+
+- BREAKING CHANGE: Remove support for EoL Ruby 2.7
+
+- ADDED: Remove support for EoL Ruby 2.7
+
 ### v1.10.0 / 2023-05-30
 
-* FIXED: Warning messages from gem build 
+- FIXED: Warning messages from gem build
 
 ### v1.8.0 / 2022-01-06
 
-* (No significant changes)
+- (No significant changes)
 
 ### v1.6.1 / 2021-09-29
 
-* (No significant changes)
+- (No significant changes)
 
 ### v1.6.0 / 2021-08-12
 
-* BREAKING CHANGE: Update opentelemetry-semantic_conventions to the 1.5.0 spec release 
+- BREAKING CHANGE: Update opentelemetry-semantic_conventions to the 1.5.0 spec release
 
-* ADDED: Update opentelemetry-semantic_conventions to the 1.5.0 spec release 
-* ADDED: Update to semantic conventions v1.6.0 
+- ADDED: Update opentelemetry-semantic_conventions to the 1.5.0 spec release
+- ADDED: Update to semantic conventions v1.6.0
 
 ### v1.4.0 / 2021-07-07
 
-* Initial release.
+- Initial release.

data/README.md

@@ -1,48 +1,113 @@
-# Opentelemetry::SemanticConventions
+# OpenTelemetry::SemanticConventions
 
-The `opentelemetry-semantic_conventions` gem provides auto-generated constants that represent the OpenTelemetry [Semantic Conventions][semantic-conventions].
+The `opentelemetry-semantic_conventions` gem provides auto-generated constants
+that represent the OpenTelemetry [Semantic Conventions][semantic-conventions].
 
 ## What is OpenTelemetry?
 
-OpenTelemetry is an open source observability framework, providing a general-purpose API, SDK, and related tools required for the instrumentation of cloud-native software, frameworks, and libraries.
+OpenTelemetry is an open source observability framework, providing a
+general-purpose API, SDK, and related tools required for the instrumentation of
+cloud-native software, frameworks, and libraries.
 
-OpenTelemetry provides a single set of APIs, libraries, agents, and collector services to capture distributed traces and metrics from your application. You can analyze them using Prometheus, Jaeger, and other observability tools.
+OpenTelemetry provides a single set of APIs, libraries, agents, and collector
+services to capture distributed traces and metrics from your application. You
+can analyze them using Prometheus, Jaeger, and other observability tools.
 
 ## How does this gem fit in?
 
-The `opentelemetry-semantic_conventions` gem provides auto-generated constants that represent the OpenTelemetry Semantic Conventions. They may be referenced in instrumentation or end-user code in place of hard-coding the names of the conventions. Because they are generated from the YAML models in the specification, they are kept up-to-date for you.
+The `opentelemetry-semantic_conventions` gem provides auto-generated constants
+that represent the OpenTelemetry Semantic Conventions. They may be referenced
+in instrumentation or end-user code in place of hard-coding the names of the
+conventions. Because they are generated from the YAML models in the
+specification, they are kept up-to-date for you.
 
 ## How do I get started?
 
 Install the gem using:
 
-```
+```sh
 gem install opentelemetry-semantic_conventions
 ```
 
-Or, if you use Bundler, include `opentelemetry-semantic_conventions` in your `Gemfile`.
+Or, if you use Bundler, include `opentelemetry-semantic_conventions` in your
+`Gemfile`.
+
+## How do I use the gem?
+
+The gem's versions match the corresponding
+[OpenTelemetry Semantic Convention versions][semconv].
+
+In version 1.36.0, we established a new pattern for naming the constants:
+* `OpenTelemetry::SemConv::Incubating::#{CATEGORY_NAME}` is the prefix for
+experimental, development, or deprecated constants
+* `OpenTelemetry::SemConv::#{CATEGORY_NAME}` is the prefix for stable constants
+
+Incubating constants will never be removed. If an incubating constant becomes
+stable, it will be copied into the stable namespace and the value will be
+available from two constants. The new constant's name will be the same, except
+the `Incubating` namespace will be removed.
+
+Prior to 1.36.0 (last version 1.11.0), constants follow a different naming
+pattern: `OpenTelemetry::SemanticConventions::#{CATEGORY_NAME}`
+
+These constants will be preserved to avoid breaking changes for users who rely
+on the old constants. These constants do not differentiate between stable and
+unstable constants. New constants will not be added to this namespace.
+
+We recommend you require only the files that contain the constants you are going
+to use. For example, if you were creating instrumentation for an HTTP Client
+that emits only stable conventions, you would likely require:
 
+```rb
+require 'opentelemetry/semconv/http'
+```
+
+If you want to require all of the 1.11.0 constants, you can use:
 ```rb
 require 'opentelemetry/semantic_conventions'
 
 # Use the constants however you feel necessary, eg:
 
-puts "This is the value of #{OpenTelemetry::SemanticConventions::Trace::CODE_LINENO}"
+puts "This is the value of #{OpenTelemetry::SemanticConventions::Trace::DB_USER}"
 ```
 
+The constant names can be very long. You can consider aliasing the long bit in
+another constant to save your fingertips some trouble.
+
+```rb
+SEMCONV_HTTP_INC = OpenTelemetry::SemConv::Incubating::HTTP
+
+SEMCONV_HTTP_INC::HTTP_REQUEST_METHOD # which would return 'http.request.method'
+```
+
+## What's up with the gem's versions?
+
+This gem doesn't follow semantic versioning. Instead, the version matches the
+upstream [OpenTelemetry Semantic Conventions version][semconv].
+
 ## How do I rebuild the conventions?
 
-Bump the version number in the Rakefile, and then run `rake generate`.
+To build the library against a new version of the semantic conventions, update SPEC_VERSION in the Rakefile, and then run `rake generate`.
+
+Do not update the library's VERSION in version.rb.
+That will be handled by the automation for releasing the gem.
 
 ## How can I get involved?
 
-The `opentelemetry-semantic_conventions` gem source is on github, along with related gems.
+The `opentelemetry-semantic_conventions` gem source is on GitHub, along with
+related gems.
 
-The OpenTelemetry Ruby gems are maintained by the OpenTelemetry-Ruby special interest group (SIG). You can get involved by joining us in [GitHub Discussions][discussions-url] or attending our weekly meeting. See the meeting calendar for dates and times. For more information on this and other language SIGs, see the OpenTelemetry community page.
+The OpenTelemetry Ruby gems are maintained by the OpenTelemetry-Ruby special
+interest group (SIG). You can get involved by joining us in
+[GitHub Discussions][discussions-url] or attending our weekly meeting. See the
+meeting calendar for dates and times. For more information on this and other
+language SIGs, see the OpenTelemetry community page.
 
 ## License
 
-The `opentelemetry-semantic_conventions` gem is distributed under the Apache 2.0 license. See LICENSE for more information.
+The `opentelemetry-semantic_conventions` gem is distributed under the Apache 2.0
+license. See LICENSE for more information.
 
 [discussions-url]: https://github.com/open-telemetry/opentelemetry-ruby/discussions
-[semantic-conventions]: https://github.com/open-telemetry/opentelemetry-specification/tree/main/semantic_conventions
+[semantic-conventions]: https://github.com/open-telemetry/semantic-conventions
+[semconv]: https://opentelemetry.io/docs/specs/semconv/