Keycloak 24.0.1 release

cache/releases/24.0.1/changelog.json

@@ -0,0 +1 @@
+[ ]

cache/releases/24.0.1/gh-release-notes.html

@@ -0,0 +1,35 @@
+<div>
+    <h2>Highlights</h2>
+<div class="sect2">
+<h3 id="_operator_deploys_nightly_build_instead_of_24_0_0">Operator deploys nightly build instead of 24.0.0</h3>
+<div class="paragraph">
+<p>Due to an issue in the release process when deploying Keycloak using the Operator it installed the <code>nightly</code> container
+instead of <code>24.0.0</code>.</p>
+</div>
+<div class="paragraph">
+<p>As a quick fix to the issue, the <code>24.0.0</code> container was tagged with <code>nightly</code>, and the <code>nightly</code> releases was temporarily
+disabled.</p>
+</div>
+<div class="paragraph">
+<p>If you installed or upgraded to <code>24.0.0</code> 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:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code>SELECT * from migration_model WHERE version = '999.0.0';</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>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:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code>UPDATE migration_model SET version = '24.0.0' WHERE version = '999.0.0';</code></pre>
+</div>
+</div>
+</div>
+<h2>Upgrading</h2>
+<p>Before upgrading refer to <a href="file:/home/runner/work/keycloak-rel/keycloak-rel/target/web/docs/latest/upgrading/index.html#migration-changes">the migration guide</a> for a complete list of changes.</p>
+
+</div>

cache/releases/24.0.1/release-notes.html

@@ -0,0 +1,29 @@
+<div class="sect2">
+<h3 id="_operator_deploys_nightly_build_instead_of_24_0_0">Operator deploys nightly build instead of 24.0.0</h3>
+<div class="paragraph">
+<p>Due to an issue in the release process when deploying Keycloak using the Operator it installed the <code>nightly</code> container
+instead of <code>24.0.0</code>.</p>
+</div>
+<div class="paragraph">
+<p>As a quick fix to the issue, the <code>24.0.0</code> container was tagged with <code>nightly</code>, and the <code>nightly</code> releases was temporarily
+disabled.</p>
+</div>
+<div class="paragraph">
+<p>If you installed or upgraded to <code>24.0.0</code> 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:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code>SELECT * from migration_model WHERE version = '999.0.0';</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>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:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="highlight"><code>UPDATE migration_model SET version = '24.0.0' WHERE version = '999.0.0';</code></pre>
+</div>
+</div>
+</div>

pom.xml

@@ -21,7 +21,7 @@
         <version.commons-io>2.11.0</version.commons-io>
         <version.commons-compress>1.26.0</version.commons-compress>
 
-        <version.keycloak>24.0.0</version.keycloak>
+        <version.keycloak>24.0.1</version.keycloak>
 
         <version.frontend-maven-plugin>1.12.1</version.frontend-maven-plugin>
         <version.node>v16.13.1</version.node>

versions/24.0.1.json

@@ -0,0 +1,7 @@
+{
+  "date": "2024-03-05",
+  "version": "24.0.1",
+  "blogTemplate": 3,
+  "documentationTemplate": 11,
+  "downloadTemplate": 23
+}