libre.sh/keycloak-scim
3
0
Fork 0
Code Issues 15 Pull requests Releases Packages Activity Actions

Added release notes for 24.0.1 (#27524)

Browse source 
Signed-off-by: stianst <stianst@gmail.com>
This commit is contained in:
Stian Thorgersen 2024-03-05 08:46:10 +01:00 committed by GitHub
parent 7e41aa9880
commit d48ef8b507
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 24 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
docs/documentation/release_notes/index.adoc
View file

@ -13,6 +13,9 @@ include::topics/templates/document-attributes.adoc[]
:release_header_latest_link: {releasenotes_link_latest}
include::topics/templates/release-header.adoc[]
== {project_name_full} 24.0.1
include::topics/24_0_1.adoc[leveloffset=2]
== {project_name_full} 24.0.0
include::topics/24_0_0.adoc[leveloffset=2]

21
docs/documentation/release_notes/topics/24_0_1.adoc Normal file
View file

@ -0,0 +1,21 @@
= Operator deploys nightly build instead of 24.0.0
Due to an issue in the release process when deploying Keycloak using the Operator it installed the `nightly` container
instead of `24.0.0`.
As a quick fix to the issue, the `24.0.0` container was tagged with `nightly`, and the `nightly` releases was temporarily
disabled.
If you installed or upgraded to `24.0.0` using the Operator before 5pm CET yesterday the database may have been updated
with the wrong versions. To check if you are affected connect to your database and run the following SQL command:
```
SELECT * from migration_model WHERE version = '999.0.0';
```
If the above returns a matching row you will need to take some actions, otherwise database migrations will not run for
future releases. To resolve this run the following SQL command:
```
UPDATE migration_model SET version = '24.0.0' WHERE version = '999.0.0';
```