The aim is to always be backwards compatible, and deprecate rather than
Non-public APIs are not covered. For example only user storage SPI is a
public API, while other SPIs like event listener is private and as such we
reserve the right to break it.
On Tue, 11 Jun 2019 at 06:01, Justin Gross <jgross.biz(a)gmail.com> wrote:
Marek Posolda brought up a good point in another thread about
pieces of Keycloak being guaranteed to have backward compatibility. Is
there a guideline for this, a strict outline of what is guaranteed to
continue being backwards compatible or any documentation outlining what
should be kept strictly compatible during a version change?
I recognize and understand the semantic versioning (or at least presume
to) however I ask this so that I can make sure I consider the list of
sacred things (if there is one) and especially take this into account while
I design/propose/work on anything within the Keycloak project. I tried
Google searching but only found the upgrade docs at
keycloak-dev mailing list