Repository navigation
chore: upgrade to Quarkus 3.37.3 and align dependency versions - #993
Conversation
ehsavoie
commented
Jul 23, 2026
ehsavoie
commented
- Quarkus 3.36.3 -> 3.37.3
- protobuf-java 4.33.2 -> 4.35.0 (required by gRPC 1.81.0 gencode)
- JUnit 6.0.3 -> 6.1.1
- rest-assured 6.0.0 -> 6.0.1
- JBang example: OpenTelemetry SDK 1.55.0 -> 1.60.1, gRPC Netty 1.77.0 -> 1.81.0
- Quarkus 3.36.3 -> 3.37.3 - protobuf-java 4.33.2 -> 4.35.0 (required by gRPC 1.81.0 gencode) - JUnit 6.0.3 -> 6.1.1 - rest-assured 6.0.0 -> 6.0.1 - JBang example: OpenTelemetry SDK 1.55.0 -> 1.60.1, gRPC Netty 1.77.0 -> 1.81.0 Signed-off-by: Emmanuel Hugonnet <ehugonne@redhat.com>
|
Does the protobuf upgrade work with the gRPC version in WildFly, for A2A-jakarta? |
|
@kabir yes, I wanted your feedback there :) |
kabir
left a comment
kabir
left a comment
There was a problem hiding this comment.
I've verified that a2a-jakarta works with these changes, and the grpc feature pack changes.
But I think we should hold off on merging this until we have the grpc feature pack release
kabir
left a comment
kabir
left a comment
There was a problem hiding this comment.
Actually, it seems a2a-jakarta works fine against this PR without the WildFly grpc feature pack upgrade.
My guess is that as the protobuf/grpc classes were generated with an older version, it runs fine on the version that the WildFly grpc feature pack has.
And I think once released, we don't regenerate the generated classes with newer versions.
When the next version of the spec is out, we will use whatever grpc/protobuf version we have installed to generate the classes for that version
3 participants
