# Keycloak 24.0.1 released

DevFeed: [Keycloak 24.0.1 released](<https://devfeed.tech/articles/keycloak-24-0-1-released-31636.md>)

Original publisher: [Read original article](<https://www.keycloak.org/2024/03/keycloak-2401-released>)

Author: Keycloak Team

Published: 2024-03-05T00:00:00Z

Content type: release

Language: en

Sources: [Keycloak Blog](<https://devfeed.tech/sources/keycloak-blog.md>)

Topics: [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [releases](<https://devfeed.tech/topics/releases.md>), [Database](<https://devfeed.tech/topics/database.md>), [SQL](<https://devfeed.tech/topics/sql.md>), [migration](<https://devfeed.tech/topics/migration.md>)

Tags: [database](<https://devfeed.tech/tags/database.md>), [idm](<https://devfeed.tech/tags/idm.md>), [kerberos](<https://devfeed.tech/tags/kerberos.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [keycloak-release](<https://devfeed.tech/tags/keycloak-release.md>), [ldap](<https://devfeed.tech/tags/ldap.md>), [migration-guide](<https://devfeed.tech/tags/migration-guide.md>), [openid-connect](<https://devfeed.tech/tags/openid-connect.md>), [release](<https://devfeed.tech/tags/release.md>), [releases](<https://devfeed.tech/tags/releases.md>), [saml](<https://devfeed.tech/tags/saml.md>), [sql](<https://devfeed.tech/tags/sql.md>), [sso](<https://devfeed.tech/tags/sso.md>)

## AI overview

Keycloak 24.0.1 is released with guidance for users affected by an Operator deployment issue that installed the nightly container instead of version 24.0.0. The article provides SQL checks and a database correction before future upgrades.

## Source excerpt

To download the release go to Keycloak downloads. 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.