diff --git a/cache/releases/24.0.1/changelog.json b/cache/releases/24.0.1/changelog.json new file mode 100644 index 00000000..8878e547 --- /dev/null +++ b/cache/releases/24.0.1/changelog.json @@ -0,0 +1 @@ +[ ] \ No newline at end of file diff --git a/cache/releases/24.0.1/gh-release-notes.html b/cache/releases/24.0.1/gh-release-notes.html new file mode 100644 index 00000000..ea48e566 --- /dev/null +++ b/cache/releases/24.0.1/gh-release-notes.html @@ -0,0 +1,35 @@ +
+

Highlights

+
+

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';
+
+
+
+

Upgrading

+

Before upgrading refer to the migration guide for a complete list of changes.

+ +
\ No newline at end of file diff --git a/cache/releases/24.0.1/release-notes.html b/cache/releases/24.0.1/release-notes.html new file mode 100644 index 00000000..63d23653 --- /dev/null +++ b/cache/releases/24.0.1/release-notes.html @@ -0,0 +1,29 @@ +
+

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';
+
+
+
\ No newline at end of file diff --git a/pom.xml b/pom.xml index 780734bc..ff00e701 100644 --- a/pom.xml +++ b/pom.xml @@ -21,7 +21,7 @@ 2.11.0 1.26.0 - 24.0.0 + 24.0.1 1.12.1 v16.13.1 diff --git a/versions/24.0.1.json b/versions/24.0.1.json new file mode 100644 index 00000000..f4c160d0 --- /dev/null +++ b/versions/24.0.1.json @@ -0,0 +1,7 @@ +{ + "date": "2024-03-05", + "version": "24.0.1", + "blogTemplate": 3, + "documentationTemplate": 11, + "downloadTemplate": 23 +}