Skip to content

deps: update opentelemetry.version to v1.57.0 #4255

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
renovate-bot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

deps: update opentelemetry.version to v1.57.0 #4255

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion benchmarks/pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<junixsocket.version>2.10.1</junixsocket.version>
<opentelemetry.version>1.56.0</opentelemetry.version>
<opentelemetry.version>1.57.0</opentelemetry.version>
Copy link

@gemini-code-assist gemini-code-assist bot Dec 6, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

This version property override in the benchmarks module can cause dependency conflicts.

  1. Internal inconsistency: The opentelemetry-api and opentelemetry-context dependencies (lines 43-49) in this file do not use this version property. They will resolve to the version in the parent BOM, while the SDK artifacts use this new version. This can lead to runtime errors if the API and SDK versions are incompatible.
  2. External inconsistency: The benchmarks module depends on google-cloud-spanner, which uses the OpenTelemetry version from the parent BOM. Overriding the version here can lead to having two different versions of OpenTelemetry on the classpath during benchmark execution.

Recommendation:
To ensure consistent dependency versions across the project, it would be best to remove this local opentelemetry.version property and let all OpenTelemetry dependencies be managed by the parent dependencyManagement. If overriding is necessary for benchmarks, please ensure all io.opentelemetry artifacts in this file use this property for consistency.

<google.cloud.monitoring.version>3.81.0</google.cloud.monitoring.version>
</properties>

Expand Down