Repository navigation
Upgrade to Quarkus 3.37.4 - #51289
Conversation
There was a problem hiding this comment.
Pull request overview
Upgrades Keycloak’s Quarkus stack to 3.37.4 and applies required compatibility updates.
Changes:
- Aligns Quarkus-managed dependencies and plugins.
- Adapts OpenTelemetry HTTP client instrumentation.
- Updates tracing and logging assertions for changed upstream behavior.
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
pom.xml |
Updates Quarkus and aligned dependency versions. |
OTelHttpClientFactory.java |
Uses the renamed OpenTelemetry builder API. |
LoggingDistTest.java |
Updates telemetry-error and masking expectations. |
TracingProviderTest.java |
Accepts randomized non-sampling trace flags. |
Closes keycloak#51273 Signed-off-by: Peter Zaoral <pzaoral@redhat.com>
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.broker.KcOidcBrokerTest#loginWithExistingUserWithBruteForceEnabledKeycloak CI - Java Distribution IT (windows-latest - temurin - 17) |
There was a problem hiding this comment.
LGTM. It will be great to unblock work that has been waiting on the tls registry work from 3.36.
|
@Pepo48 why not 3.38.0 https://github.com/quarkusio/quarkus-platform/tags ? |
Because it wasn't just releasead when I was preparing this 😊 Since this one ready, tested and approved, I would proceed with it. I will prepare the 3.38 upgrade as a follow-up. |
|
@vmuzikar any objections? |
|
@Pepo48 Hi Peter! Just out of curiosity; so the Keycloak 26.8 will use the next Quarkus LTS version? |
Yes! Quarkus 3.40 is the next LTS. |
Closes #51273
Apart from the version bumps, the PR contains cherry-picked quarkus-next fixes effective in <=3.37:
Once merged, I'll remove these commits from the quarkus-next branch to avoid conflicts.