-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for 11.0.0 and drop support for 8.0.0 #357
Conversation
I assume the error is caused by this change: keycloak/keycloak@6005503
|
... and now I broke all <11.0.0.. How can we support 11.0.0 without breaking < 11.0.0? Edit: |
Yeah... I was afraid that something like this might happen due to a major release introducing breaking API changes. I haven't dug too deep in this yet, but it looks like Keycloak 11 is expecting If this is the case, then we'll have to start doing version checking at runtime instead of just doing it during tests. I can dig into this more when I have some free time. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Now all the CI is green. Could you take a look at the last commit? |
Groups path was added in 11.0.0[1], and using it with older versions doesn't work. [1] keycloak/keycloak@6005503
}, | ||
} | ||
|
||
if KeycloakVersionIsGreaterThanOrEqualTo(keycloakClient, "11.0.0") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we need this, but maybe it worth it anyway as it is more explicit.
@klausenbusk This needs a rebase. |
I think this was <somehow> fixed as part of: #369 |
#356 is currently blocked on this PR.