Metabase 64 is now the default version
Metabase 64 is available on Clever Cloud since October 9, 2026. It’s now the default version, used when CC_METABASE_VERSION is latest or isn’t set. It’s a Long Term Support (LTS) release, supported by Metabase until December 1, 2027 according to its version support policy.
Add-ons that use latest move to Metabase 64 automatically, without downtime. Add-ons pinned to a specific version or branch, such as 0.63 or 1.63, keep the version they run today until you change it.
Signed sessions for new add-ons
Every new Metabase add-on now gets a MB_SESSION_SECRET_KEY environment variable on its underlying Java application. With this secret, Metabase signs the session keys it stores in its application database, so database access alone is no longer enough to create or use a valid session.
Existing add-ons don’t get this variable automatically. To enable it, set a value of at least 16 characters on the Java application and restart it. Setting or changing this value logs out all active sessions:
clever env set MB_SESSION_SECRET_KEY "$(openssl rand -base64 32)" --app yourMetabaseJavaApp
clever restart --app yourMetabaseJavaAppHow to update a pinned add-on
You can update through the add-on’s dashboard in the Clever Cloud Console. You can also set CC_METABASE_VERSION of the underlying Java application to latest, 0.64 or 1.64 for the enterprise edition (EE) and rebuild it without the build cache, or use Clever Tools:
clever features enable operators
clever metabase version check yourMetabaseNameOrId
clever metabase version update yourMetabaseNameOrId --target 0.64