Metabase Releases: Track Versions, LTS Support & Upgrades

Metabase releases happen on a predictable schedule: new stable versions every 2 months, with long-term support (LTS) versions receiving security patches for 14 months. The current stable release is v0.64.4 (open source) released October 30, 2026. You track releases on GitHub, metabase.com/releases, and Docker Hub. Upgrading takes one command in Docker and usually completes within a minute.

Understanding Metabase's Release Model

Metabase uses a dual versioning scheme that confuses many users. Open source editions use the 0.x scheme (v0.64.4). Enterprise editions use the 1.x scheme (v1.65.2). Both versions release on the same schedule and include identical features; the difference is licensing and support structure.

Within each version line, Metabase distinguishes between standard releases and LTS (long-term support) releases. Standard releases receive about 2 months of security updates before they fall off the support cycle. LTS releases stay supported for 14 months. Version 64, released September 16, 2026, carries the LTS badge. If you deploy v0.64.4 today, you will receive patches until December 1, 2027. This gives teams confidence that they won't be forced to upgrade for over a year.

Every Metabase release includes features, bug fixes, and sometimes breaking changes that affect existing queries or dashboards. The feature set is identical between OSS (0.x) and Enterprise (1.x) at the same version number. The version numbers are offset by one between the two editions: v1.65 and v0.64 ship the same features at the same time.

New releases deploy on the second Monday of each month, unless a security patch forces an unscheduled release. You can check the GitHub releases page or metabase.com/releases for the exact date and feature summary for any version. This predictability lets you plan upgrades in advance and avoid surprises.

Finding Metabase Releases

Metabase publishes release information across three canonical sources. No single place holds everything, so learning to use all three saves time when you are tracking down a specific version or feature.

GitHub (github.com/metabase/metabase/releases) lists every release with the date, Docker image tags for both OSS and Enterprise, JAR download links, and a link to the detailed changelog. This is the primary source of truth for release artifacts. Each release shows separate image tags: metabase/metabase:v0.64.4 for OSS and metabase/metabase-enterprise:v1.65.2 for enterprise. You can pull a specific version tag here, and all 46,092 commits are available via GitHub if you need to audit the code.

Metabase.com/releases shows a timeline view organized by year. Each release includes the month, version number, and a bulleted list of 3-6 major features introduced in that version. Many teams read this page monthly to understand what changed in a recent release without diving into GitHub. If you need the detailed changelog for a release, click "Read more" to access the full technical notes and breaking-change warnings.

Docker Hub (hub.docker.com/r/metabase/metabase) shows all available image tags and the last-modified date for each. The "latest" tag always points to the most recent stable release. If you are running docker-compose or a Kubernetes deployment and want to pin a specific version, you pull a named tag instead of "latest". This prevents accidental upgrades when you redeploy.

Endoflife.date/metabase shows a table of every version released, with the release date, end-of-life date for security support, and the latest patch version in each release line. This tracker is useful for understanding whether a version you are running has reached end-of-life and no longer receives patches. Version 64 (LTS, released Sep 16, 2026) shows support ending December 1, 2027. Versions older than 64 are nearing or past end-of-life.

Checking Your Current Metabase Version

Knowing which version you run is the first step before deciding to upgrade. Metabase stores this information in the UI, in Docker logs, and in the JAR filename.

In the Metabase web interface, click the gear icon (settings) in the top right corner and scroll to "About Metabase". You will see "Version x.y.z" displayed prominently. This is the fastest way if you have access to the Metabase admin panel. The version appears exactly as it was released, e.g., "0.64.4".

In Docker, run docker logs <container-id> | grep "Metabase started" and search for the version number in the startup output. The log shows the exact version the container booted with. Alternatively, docker inspect <container-id> | grep Image shows the image tag you deployed. If you pinned a version (e.g., metabase/metabase:v0.64.4), the tag will reveal your version immediately.

If you downloaded the JAR directly, the version is in the filename. The Metabase JAR is either named metabase.jar (generic, latest version) or metabase-v0.64.4.jar (pinned, specific version). You can also run java -jar metabase.jar --version to print the version to stdout.

Once you know your current version, compare it against endoflife.date/metabase to see whether your version is still receiving security updates. If you are running v0.62 or older, security patches have likely ended. Upgrading to v0.64 (LTS) is worth planning.

What Changed: Recent Releases

Metabase v0.64 (LTS, released September 16, 2026) added field validation, improvements to drill-through queries, and better handling of date filters across databases. This is the current long-term support version. If stability matters more than new features, stay on v64 and receive updates until December 2027.

Metabase v0.63 (released August 19, 2026) introduced native query editing improvements and simplified the setup flow for new database connections. Performance on large dashboards improved. Support for v63 ends around October 2026, so upgrading to v64 should be on your calendar soon.

Metabase v0.62 (released July 22, 2026) brought significant changes to data permissions and dashboard caching behavior. If you skipped this version and jumped directly to v64, read the breaking-changes section on metabase.com/releases before upgrading. Dashboard cache invalidation works differently in v62+.

On August 6, 2026, Metabase released a security update addressing a vulnerability in the query execution pipeline that could allow unauthorized database access in specific configurations. Details are available on the Metabase security advisory page. If you run a version released before August 6, 2026, and the vulnerability affects your setup, upgrade immediately. Security releases are not tied to the regular monthly cycle; they can ship anytime.

You can view the full feature list and breaking changes for any release on metabase.com/releases. Click any version number to expand the detailed changelog. This is where you discover whether a new version breaks your existing dashboards or changes behavior you rely on.

Upgrade Strategies for Docker

Docker is the most common way to run self-hosted Metabase in production. Upgrading requires two decisions: whether to pin a version and how much downtime you can tolerate.

To upgrade with the "latest" tag (simplest approach for non-production), update your docker-compose.yml so the image line reads image: metabase/metabase:latest, then run docker-compose pull && docker-compose up -d. Docker pulls the latest stable image and restarts the container. This takes 30-60 seconds of downtime while Metabase starts. Your database is left untouched; Metabase performs schema migrations automatically on startup.

To upgrade to a specific version, replace "latest" with the version tag: image: metabase/metabase:v0.64.4. This is safer for production if you want to test a version before committing to it permanently. After updating docker-compose.yml, run the same docker-compose pull && docker-compose up -d commands. Metabase will start the new version and run any required database migrations.

To pin a version in production and avoid accidental upgrades, set a specific tag and never use "latest". Example: image: metabase/metabase:v0.64.4. Update your docker-compose.yml manually when you are ready to upgrade, test in a staging environment, and then deploy. This prevents the chaos of automatic upgrades in production.

Before upgrading any Metabase version, back up your application database (the database where Metabase stores queries, dashboards, and metadata). Metabase can usually roll back by reverting the docker-compose.yml and restarting with the old version, but a backup is always safer. If a migration fails or a new version introduces a bug, a backup lets you restore your work.

For Metabase running on Kubernetes or other orchestration platforms, the same principles apply: update the image tag in your deployment manifest and apply it. Use specific version tags (v0.64.4) in production, never "latest". Test upgrades in staging first. Monitor the new version for 2-3 days before declaring the upgrade successful.

Security Releases & Critical Patches

Metabase publishes security advisories on metabase.com/security whenever a vulnerability is discovered. When a critical vulnerability is found, the team releases a patch outside the normal monthly cycle, sometimes within hours of discovery.

On August 6, 2026, Metabase released a security update addressing a vulnerability in query execution that could allow unauthorized database access in specific setups with specific configurations. The advisory included the affected versions, the exact conditions under which the vulnerability applied, and a recommendation to upgrade immediately. If you were running a version released before the patch date and the vulnerability applied to your setup, your instance was vulnerable for the time between the discovery and your upgrade.

To stay informed about security releases, watch the GitHub repository (click "Watch" > "Custom" > select "Releases" only) or subscribe to the Metabase mailing list. Many teams monitor the Metabase community forum (discourse.metabase.com) for security announcements and upgrade discussions.

Security patches are backported to LTS versions and recent standard releases. If you run an old, unsupported version, you will not receive patches. This is a key reason to upgrade to an LTS version at least every 14 months. Staying on v0.64 until December 2027 guarantees security updates for that full period.

Staying Informed About New Releases

You have several options to be notified when Metabase releases a new version. The best approach depends on how much detail you want and how often you are willing to check.

Watch the GitHub repository (github.com/metabase/metabase): Click the "Watch" button in the top right, select "Custom", and check the "Releases" option only. You will get an email notification for every new release, including release notes and download links.

Follow endoflife.date/metabase: Bookmark this page and check it once a month. The "Updated" timestamp shows when the page last refreshed. You can also set a calendar reminder to visit the page on the first of each month.

Check metabase.com/releases monthly: Scroll to the latest release and read the feature summary and breaking-change section. If a feature or fix matters to your team, add an upgrade task to your backlog.

Join the Metabase community forum (discourse.metabase.com) and read the "Announcements" category. The Metabase team posts releases there, discusses major breaking changes, and answers upgrade questions.

Set a Google Alert for "metabase release" to catch third-party coverage and blog posts about new versions. This catches adoption stories and known issues reported by other teams.

You do not need to upgrade immediately after a release. The standard practice is to wait 1-2 weeks, monitor for bug reports, then test the upgrade in a staging environment before deploying to production. This reduces the risk of hitting an undiscovered bug that the team will fix in a patch release.

When Managed Hosting Wins

Tracking Metabase releases, planning upgrades, managing downtime, and backing up your database requires time and attention. For teams with fewer than 3 people managing infrastructure, or those running Metabase on production data where downtime is costly, managed Metabase hosting is worth evaluating.

Opsily's managed Metabase handles upgrades automatically on a schedule you choose: nightly, weekly, or monthly. You have zero downtime during the upgrade because Opsily uses blue-green deployment strategies. The version stays current, and your data is backed up before any upgrade runs. You are freed from the release-tracking work entirely and can focus on analytics.

For self-hosted Metabase, you own the upgrade planning, testing, and rollback risk. For managed hosting, the vendor owns it. Opsily monitors releases and patches automatically. The choice depends on whether you have the ops capacity in-house. Small teams typically find managed hosting less expensive than the time cost of DIY upgrading. See Opsily's managed Metabase hosting for details on how automatic upgrades work.

Frequently Asked Questions

How do I check what version of Metabase I'm running?

Click the settings icon (gear) in the top right of the Metabase UI and scroll to "About Metabase". You will see your version number immediately. If you run Metabase in Docker, check the startup logs with docker logs <container-id> | grep "Metabase started" to see the version.

What is the difference between Metabase OSS and Enterprise versions?

Metabase OSS (open source, 0.x versions) is free and includes all core analytics features. Enterprise (1.x versions) adds paid features like single sign-on, advanced permissions, and white-label dashboards. The 0.x and 1.x versions release on the same schedule and include the same data analysis features. OSS is sufficient for most teams and small businesses.

How do I upgrade Metabase safely?

Back up your Metabase application database first. For Docker deployments, update the image tag in docker-compose.yml to the new version, then run docker-compose pull && docker-compose up -d. Metabase will run schema migrations automatically on startup. Test the upgrade in a staging environment before deploying to production.

What is the Metabase release schedule?

Metabase publishes a new stable release on the second Monday of each month, unless a security vulnerability forces an unscheduled release. Standard versions receive security patches for about 2 months. LTS versions (currently v64) receive patches for 14 months. See endoflife.date/metabase for the exact support end dates for each version.

How do I pin a specific Metabase version in Docker?

In your docker-compose.yml, set the image to a specific tag instead of "latest": image: metabase/metabase:v0.64.4. This prevents automatic upgrades when you run docker-compose pull. You upgrade manually by changing the tag in the file and restarting the container.

What are LTS releases, and which Metabase versions have LTS support?

LTS (long-term support) releases receive security patches for 14 months instead of 2 months. Version 64 (released September 16, 2026) is the current LTS release and will be supported until December 1, 2027. Future LTS releases are typically chosen every 12-16 months. Check endoflife.date/metabase for the full LTS schedule and upcoming LTS versions.

How do I get notified about Metabase security updates?

Watch the GitHub repository (metabase/metabase) and select "Custom" notifications for "Releases" only. You will get an email for every new release, including security patches. Alternatively, subscribe to the Metabase mailing list or check their security advisory page (metabase.com/security) monthly.

What breaks when I upgrade Metabase?

Breaking changes are rare but documented in the release notes on metabase.com/releases. Common issues include dashboard permission changes in v63, query caching behavior changes in v62, and data type handling in filters. Always read the "Breaking Changes" section of the release notes before upgrading. Test the upgrade in a staging environment first to catch issues before production.

The Bottom Line

Metabase releases follow a predictable monthly schedule with clear version support dates. The current stable version is v0.64.4 with LTS support until December 2027. You can find releases on GitHub, metabase.com/releases, and Docker Hub. Upgrading in Docker takes one command. The tradeoff is between keeping up with releases yourself and reducing operational overhead. When managed Metabase hosting makes sense, Opsily handles the upgrade schedule and takes the operational burden entirely off your team.