Skip to content

deps: update opentelemetry.version to v1.60.0 #4379

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
+1 −1
Open

deps: update opentelemetry.version to v1.60.0 #4379

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.59.0</opentelemetry.version>
<opentelemetry.version>1.60.0</opentelemetry.version>
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Mar 7, 2026

Choose a reason for hiding this comment

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

high

While this version update is correct, it highlights an underlying issue with how OpenTelemetry dependencies are managed in this pom.xml.

Some dependencies like opentelemetry-api (line 43) inherit their version from parent POMs, while others like opentelemetry-sdk (line 67) use this explicit ${opentelemetry.version} property. This can lead to a mix of different OpenTelemetry versions on the classpath, potentially causing runtime errors like NoSuchMethodError.

To ensure version consistency, I recommend using the OpenTelemetry BOM to manage all io.opentelemetry dependencies. You can do this by adding the BOM to a <dependencyManagement> section and removing the explicit <version> tags from individual dependencies.

Example of importing the BOM:

<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>io.opentelemetry</groupId>
      <artifactId>opentelemetry-bom</artifactId>
      <version>${opentelemetry.version}</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  </dependencies>
</dependencyManagement>

This will ensure all OpenTelemetry artifacts are on the same version and will simplify future updates.

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

Expand Down