chore(deps): Bump opentelemetry-proto to 1.11.0-alpha and protobuf to 4.35.1 - #25472
Merged
Conversation
… 4.35.1 Bump opentelemetry-proto from 1.10.0-alpha to 1.11.0-alpha. Also bump protobuf from 4.34.2 to 4.35.1 as the new otel proto was generated with protobuf 4.35.1 and requires a matching runtime. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Claus Ibsen <claus.ibsen@gmail.com>
Contributor
|
🌟 Thank you for your contribution to the Apache Camel project! 🌟 🐫 Apache Camel Committers, please review the following items:
|
Contributor
|
🧪 CI tested the following changed modules:
✅ POM dependency changes: targeted tests included Changed properties: opentelemetry-proto-version,protobuf-version Modules affected by dependency changes (5)
🔬 Scalpel shadow comparison — Scalpel: 45 tested, 29 compile-only — current: 0 all testedMaveniverse Scalpel detected 74 affected modules (current approach: 0).
|
gnodet
approved these changes
Aug 12, 2026
gnodet
left a comment
gnodet
left a comment
Contributor
There was a problem hiding this comment.
Clean, well-motivated dependency upgrade. Both bumps are correctly paired — opentelemetry-proto-java 1.11.0-alpha was compiled with protobuf 4.35.1, so both must move together to avoid runtime class initialization failures.
Verified:
- opentelemetry-proto 1.10.0-alpha → 1.11.0-alpha: upstream OTLP v1.11.0 adds a new
ProcessContextmessage and documentation for request/response size limits. All changes are additive; no removals, no breaking API changes. Classes used bycamel-opentelemetry2are unchanged. - protobuf-java 4.34.2 → 4.35.1: v35.0 Java changes are minor (
BytecodeClassNamefunctions,JsonFormatfix for large exponents). v35.1 had zero Java-specific changes. Standard protobuf APIs used across the codebase are all stable. - Version alignment is correct:
opentelemetry-proto-java1.11.0-alpha declares protobuf 4.35.1 in its own build, so bumping Camel's protobuf version to match eliminates any runtime version mismatch. - Both properties defined once in
parent/pom.xmland referenced consistently across all consuming modules. - CI green on both JDK 17 and JDK 25.
This review was generated by an AI agent and may contain inaccuracies. Please verify all suggestions before applying.
Claude Code on behalf of @gnodet
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
2 participants
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.
Summary
Claude Code on behalf of davsclaus
opentelemetry-protofrom 1.10.0-alpha to 1.11.0-alphaprotobuffrom 4.34.2 to 4.35.1The new
opentelemetry-proto 1.11.0-alphawas generated with protobuf 4.35.1 and requires a matching runtime version (protobuf rejects older runtimes at class initialization). Both bumps are needed together.Supersedes #25192.
Test plan
camel-opentelemetry2— all 37 tests pass (was 10 errors with proto bump alone)camel-protobuf— all tests pass🤖 Generated with Claude Code
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com