-
|
Does the keycloak-js npm package releases follow the releases of keycloak? I was hoping to see a new version of keycloak-js published sooner rather than later, as there is a VERY small change in the nightly builds that hasn't been cut into a release yet. Here is the change we need: cdef39f I'm coming from the keycloak-angular repo, where this issue was reported over there - mauriciovigolo/keycloak-angular#395 |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 1 reply
-
|
@gwin003 keycloak-js is released with other Keycloak artifacts, like Keycloak Server, Keycloak Operator, Keycloak Node.js. The next release should be out soon. |
Beta Was this translation helpful? Give feedback.
-
|
@abstractj I noticed there was a keycloak release (18.0.1) on Jun 16, but it appears the keycloak-js artifact was not updated in 18.0.1? This change is still not present. cdef39f |
Beta Was this translation helpful? Give feedback.
-
|
@gwin003 that's strange because I can see the release on npmjs (https://www.npmjs.com/package/keycloak-js). Would you be able to create a GH issue with all the details? In this way we don't miss it. |
Beta Was this translation helpful? Give feedback.
-
|
@abstractj I can also see it there, so thats not the issue. The issue is that the 18.0.1 release, which was published on June 16th, does not contain the fix I linked above, which was committed on May 12th. Unless I'm totally missing something, I'd expect that KeycloakInitOptions |
Beta Was this translation helpful? Give feedback.
-
|
I created an issue to track this. #12945 |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @gwin003! |
Beta Was this translation helpful? Give feedback.
@gwin003 keycloak-js is released with other Keycloak artifacts, like Keycloak Server, Keycloak Operator, Keycloak Node.js. The next release should be out soon.