Repository navigation
Conversation
|
|
Hi, and thanks for maintaining this project — it does a lot of heavy lifting on our side. Would it be possible to get a review on this PR? It has been open since 6 August; CI is green and it still merges cleanly. For context on why we are following it closely: the latest release (6.5.1) supports Keycloak up to 26.5.5, while Keycloak is now at 26.7.4. We use keycloak-config-cli in production for realm-as-code, so we are keeping our Keycloak server pinned to 26.5.5 until a matching config-cli tag exists — a realm exported from a newer server is not accepted by the current client model, so upgrading the server first is not an option for us. We understand maintenance time is limited and we are not trying to rush anyone. If it helps, we are glad to test this branch against a live 26.7.x realm and report back. One small suggestion: 26.7.4 may now be a better target than 26.7.0. Thanks a lot! |
|
@AssahBismarkabah can you maybe have look ? |
|
any chance that one gets merged soon? |
|
maybe time to create a fork of this projects not response from the mainters ? |
|
This branch has not been deployed
4 participants
What this PR does / why we need it:
Upgrade to latest Keycloak Version, to support all new config fields.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged): fixes #1666How this PR was tested:
Special notes for your reviewer:
PR Readiness Checklist:
Complete these before marking the PR as
ready to review:mvn testor relevant subset)CHANGELOG.mdrelease notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR