Repository navigation
Extended release support
#52655
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
- 5EEF
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Keycloak currently only supports the latest release. This essentially means when there is a new major or minor release users are forced to upgrade immediately to receive any new security or bug fixes.
For major releases that are expected to introduce breaking changes and removing deprecated features, this is not sustainable. A successful migration to a new major release can take anything from days to months depending on the use-case and capacity.
With Keycloak 27.0 being released in 2027 we are planning to support 26.x for around 6 months after 27.0 is released. The last release of 26.x is planned to be 26.8, that effectively means 26.8 would be supported for around 12 months in total.
For minor releases on the other hand that does not solve the problem. Even though we strive for seamless upgrades between minor releases, this is not something we can always guarantee. Upgrading to a new minor release takes days to weeks in most cases, but can also take months in some more extended use-cases (for example for those using a lot of customisation and extensions).
In Keycloak 27.x we would like to improve on this situation by delivering some overlap between minor releases. This will only be applicable to 27.x (and future major releases), and not to 26.x.
For that we have a few different proposals that we would like feedback on to figure out what solution best serves the Keycloak community. Due to the ever growing community size, and increasing amount of security issues reported, we do not have capacity to deliver multiple options, and may also not pick the most popular option voted by the community (although we will strive to do so).
The options we have identified are:
For comments and questions around this see #52656 and #51010
62 votes ·
All reactions