deps: update opentelemetry.version to v1.57.0

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
io.opentelemetry:opentelemetry-sdk-testing	1.56.0 -> 1.57.0
io.opentelemetry:opentelemetry-sdk-trace	1.56.0 -> 1.57.0
io.opentelemetry:opentelemetry-sdk-metrics	1.56.0 -> 1.57.0
io.opentelemetry:opentelemetry-sdk	1.56.0 -> 1.57.0

---

Release Notes

open-telemetry/opentelemetry-java (io.opentelemetry:opentelemetry-sdk-testing)

v1.57.0

API

• Add GlobalOpenTelemetry#getOrNoop, #isSet. Update #get to always returns obfuscated instance
  (#​7819)

Incubating

• Logs: Complex attributes incubating implementation
  (#​7814)

SDK

Logs

• Add minimum severity and trace-based logger configuration (incubating API)
  (#​7529)

Exporters

• OTLP: VarHandle string encoder
  (#​7701)
• OTLP: Fix OkHttpGrpcSender to properly await executor shutdown
  (#​7840)
• OTLP: avoid auto-config warning
  (#​7881)
• OTLP: update error message for missing GrpcSenderProvider dependency
  (#​7884)

Extensions

• Declarative config: add runtime hints for graal VM
  (#​7866)
• Declarative config: add missing warning about discarded value
  (#​7821)

Project tooling

• Update macos version to latest and switch to corretto for testing
  (#​7841)
• Sync Java worflows: Allow re-running prepare release branch workflow
  (#​7845)
• Simplify and standardize renovate custom managers across Java repos
  (#​7846)
• Remove misspell workflow
  (#​7852)
• Fix link checks on main
  (#​7867)
• Add zeitlinger as approver
  (#​7868)
• Move snapshot publishing to daily build
  (#​7886)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[dpebot]

/gcbrun

[gemini-code-assist]

Summary of Changes

Hello @renovate-bot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the project's OpenTelemetry dependency to version 1.57.0. This routine maintenance ensures the project benefits from the latest features, performance optimizations, and bug fixes provided by the OpenTelemetry Java SDK, enhancing observability capabilities and system stability.

Highlights

• OpenTelemetry Version Update: Updates the opentelemetry.version dependency from 1.56.0 to 1.57.0 across the project.
• OpenTelemetry API Enhancements: Includes API updates such as GlobalOpenTelemetry#getOrNoop and #isSet, and modifies #get to consistently return an obfuscated instance.
• OpenTelemetry SDK and Exporter Improvements: Introduces incubating features for complex log attributes and minimum severity configuration, alongside OTLP exporter fixes and performance enhancements.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the opentelemetry.version property in the benchmarks/pom.xml to 1.57.0. While this is a straightforward dependency update, it highlights a potential issue with dependency management in the project. The benchmarks module defines its own OpenTelemetry version, which can lead to inconsistencies with other modules and within the module itself, as not all OpenTelemetry dependencies use this property. I've left a comment with more details and suggestions for how to resolve this to prevent potential runtime issues.

[gemini-code-assist]

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.