Closed
Conversation
* opentelemetry-api 1.5.0 (was 1.4.0) * opentelemetry-registry 0.4.0 (was 0.3.1) * opentelemetry-sdk 1.8.0 (was 1.7.0) * opentelemetry-sdk-experimental 0.4.0 (was 0.3.2) * opentelemetry-common 0.22.0 (was 0.21.0) * opentelemetry-exporter-jaeger 0.24.0 (was 0.23.0) * opentelemetry-exporter-otlp 0.30.0 (was 0.29.1) * opentelemetry-exporter-otlp-logs 0.2.0 (was 0.1.0) * opentelemetry-exporter-otlp-metrics 0.4.0 (was 0.3.0) * opentelemetry-exporter-zipkin 0.24.0 (was 0.23.2) * opentelemetry-propagator-b3 0.22.0 (was 0.21.0) * opentelemetry-propagator-jaeger 0.22.0 (was 0.21.1) * opentelemetry-semantic_conventions 1.11.0 (was 1.10.1) * opentelemetry-test-helpers 0.6.0 (was 0.5.0) * opentelemetry-metrics-api 0.3.0 (was 0.2.0) * opentelemetry-metrics-sdk 0.6.0 (was 0.5.0) * opentelemetry-logs-api 0.2.0 (was 0.1.0) * opentelemetry-logs-sdk 0.2.0 (was 0.1.0)
Contributor
|
We haven't bumped the min version dependencies in a while. For example the SDK's dependencies are: spec.add_dependency 'opentelemetry-api', '~> 1.1'
spec.add_dependency 'opentelemetry-common', '~> 0.20'
spec.add_dependency 'opentelemetry-registry', '~> 0.2'which is several minor versions behind the released versions. Is this because nothing has changed in those gems that the latest SDK version depends on? |
Contributor
Author
Contributor
Author
|
WARNING: An additional commit was added while this release PR was open. Commit link: 56669f8 Message: Co-authored-by: otelbot 197425009+otelbot@users.noreply.github.com |
Contributor
|
closing this, a new PR will open tomorrow with the correct dates. |
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.
This pull request prepares new gem releases for the following gems:
For each gem, this pull request modifies the gem version and provides an initial changelog entry based on conventional commit messages. You can edit these changes before merging, to release a different version or to alter the changelog text.
The generated changelog entries have been copied below:
opentelemetry-api
v1.5.0 / 2025-02-18
opentelemetry-registry
v0.4.0 / 2025-02-18
opentelemetry-sdk
v1.8.0 / 2025-02-18
opentelemetry-sdk-experimental
v0.4.0 / 2025-02-18
opentelemetry-common
v0.22.0 / 2025-02-18
opentelemetry-exporter-jaeger
v0.24.0 / 2025-02-18
opentelemetry-exporter-otlp
v0.30.0 / 2025-02-18
opentelemetry-exporter-otlp-logs
v0.2.0 / 2025-02-18
opentelemetry-exporter-otlp-metrics
v0.4.0 / 2025-02-18
opentelemetry-exporter-zipkin
v0.24.0 / 2025-02-18
opentelemetry-propagator-b3
v0.22.0 / 2025-02-18
opentelemetry-propagator-jaeger
v0.22.0 / 2025-02-18
opentelemetry-semantic_conventions
v1.11.0 / 2025-02-18
opentelemetry-test-helpers
v0.6.0 / 2025-02-18
opentelemetry-metrics-api
v0.3.0 / 2025-02-18
opentelemetry-metrics-sdk
v0.6.0 / 2025-02-18
opentelemetry-logs-api
v0.2.0 / 2025-02-18
opentelemetry-logs-sdk
v0.2.0 / 2025-02-18