This is documentation for the next version of Grafana. For the latest stable release, go to the latest version.

Documentation Grafana documentation Upgrade Grafana Upgrade strategies

Strategies for upgrading your self-managed Grafana instance

At Grafana Labs, we believe in shipping features early and often, and in recent years we’ve increased our commitment to that philosophy.

We no longer wait for the yearly major release to give you access to the next big improvement. Instead, we regularly make new features, bug fixes, and security patches available to our self-managing users ( Grafana OSS and Grafana Enterprise) throughout the year.

Having a dependable release process provides users like you with the best Grafana experience possible, and it provides the flexibility to upgrade in a manner that works best for you and your organization.

What to expect from each release type

We split Grafana OSS and Grafana Enterprise releases into three main categories:

• Minor release (every other month): These releases can include new features, deprecation notices, notices about upcoming breaking changes, previously announced breaking changes, bug fixes, and security vulnerability patches.
• Major release (once a year, in April/May): These are like a minor release, but accompanied by GrafanaCON and a comprehensive upgrade guide for users who like to upgrade only once a year.
• Patching release (every month): These include bug fixes for currently supported versions, as well as any security vulnerability patches.

You can choose your cadence: For frequent self-managed updates, you should follow the minor release (for example, upgrade 11.1 to 11.2), which also gives you access to the latest features. If you need a longer period to review our new releases, you should follow the major releases. Both strategies get patching releases with security fixes (high severity security fixes also result in ad-hoc patch releases). We’ll get into additional guidance on upgrade cadences later in this guide.

How to find the specifics for a release

We love sharing all our great features with you so you can leverage Grafana to its fullest. We also understand that complete release documentation allows you to upgrade with confidence. Whether it’s knowing that a bug has been fixed, seeing that a security vulnerability is patched, or understanding how to mitigate the impact of breaking changes, proper documentation allows you to make informed decisions about when to upgrade your local Grafana instances.

We provide release documentation in multiple places to address different needs:

• What’s new outlines new features debuting in each major and minor release.
• Breaking changes notify you of updates included in major releases that could impact you and provide mitigation recommendations when needed.
• Upgrade guides instruct you on how to upgrade to a newer minor or major version.
• And finally, a changelog is generated for every release (major, minor, patching, security) and outlines all changes included in that release.

When to expect releases

Currently, Grafana is on a monthly release cycle. Here’s a look at scheduled releases for 2025:

A few important notes

• The schedule above outlines how we plan release dates. However, unforeseen events and circumstances may cause dates to change.
• High severity security and feature degradation incidents will result in ad-hoc releases that are not scheduled ahead of time.
• Patching releases are for the current (last released) minor version of Grafana. Additional older versions of Grafana may be included if there is a critical bug or security vulnerability that needs to be patched.
• Release freezes: Each year Grafana implements two release freezes to accommodate for the holiday season. During these times, no scheduled releases will be executed. However, this does not apply to changes that may be required during the course of an operational or security incident.

Grafana security releases: improved version naming convention

We’ve enhanced our naming convention for security release versions to make it easier to clearly identify our security releases from our standard patching releases.

In the past, critical vulnerabilities triggered unscheduled releases that incremented the patch version (e.g., 10.3.0 to 10.3.1). However, we found that the naming convention for these releases didn’t clearly communicate the nature of the update. For example, if there was a version change from 11.3.0 to 11.3.1, there was no indication whether it was a security fix, a bug fix, or a minor feature update. This lack of clarity led to confusion about the urgency and nature of the update.

Our new approach directly addresses this issue. Going forward, security releases will be appended with “+security” to indicate that the release is the indicated version PLUS the security fix.

For example: A release named “11.2.3+security-01” would consist of what was released in 11.2.3 PLUS the indicated security fix. Once released, the security fix will also then be automatically included in all future releases of the impacted version.

This naming convention should make it easier to identify security updates and the Grafana version they’re based on, allowing for a better understanding of the importance and urgency of each release.

What to know about version support

Self-managed Grafana users have control over when they upgrade to a new version of Grafana. To help you make an informed decision about whether it’s time to upgrade, it’s important that you understand the level of support provided for your current version.

For self-managed Grafana (both Enterprise and OSS), the support for versions follows these rules:

• Each minor release is supported for 9 months after its release date
• The last minor release of a major version receives extended support for 15 months after its release date
• Support levels change as new versions are released:
  • Full Support: The most recently released major/minor (and the last minor of the previous major) version receive full support including new features, bug fixes, and security patches
  • Security & Critical Bugs Only: Versions that are not the most recently released major/minor (or the last minor of the previous major) version, but still within their support period, receive only security patches and critical bug fixes
  • Not Supported: Versions beyond their support period receive no updates

Here is an overview of version support through 2026:

How are these versions supported?

The level of support changes as new versions of Grafana are released. Here are the key details:

• Full Support:

  • All new features
  • All bug fixes
  • Security patches
  • Regular updates

• Security & Critical Bugs Only:

  • Security vulnerability patches
  • Critical bug fixes that cause feature degradation
  • No new features

• Not Supported: Versions beyond their support period receive no updates and should be upgraded.

Keeping all this in mind, users that want to receive the most recent features and all bug fixes should be on the current (most recently released) version of Grafana.

What is a critical feature degradation?

A critical feature degradation usually meets one of the following criteria:

• Major functionality is universally unavailable (for example, cannot create dashboards, unable to authenticate).
• Major (critical) impact to a significant amount of customers.
• Major escalated incident for one or many customers.

Self-managing upgrade strategies

Based on your needs, choose your ideal upgrade strategy. Here’s what that might look like in practice:

Follow the “minor” strategy for the most flexibility, as you can also occasionally lengthen the cadence to a full quarter and still rely on your currently deployed minor release being supported with security fixes.

How the Grafana team catches bugs and breaks during the release process

1. Each team writes automated tests for their code and we run automated tests which include unit tests, integration tests, end-to-end tests, and load tests. For plugins specifically, we test the frontend and backend parts of a data source (unit), integrating a data source with a matrix of Grafana versions (E2E), and the contract between the data source and the API it consumes (integration).
2. We perform manual acceptance and smoke testing internally for new features by deploying to our internal observability stack. After that, we progressively roll out in Grafana Cloud, and then cut an OSS and Enterprise release. Each stage catches bugs.
3. We ship new features in Experimental or Private Preview release stages, behind feature toggles. This helps us improve the feature during development. If you are interested in gaining early access to features (including in your development or test environments), please let us know.
4. We scan Grafana, all plugins and their dependencies continuously for security vulnerabilities.

Minimize the likelihood of bugs and problems during upgrade

Despite thorough testing, you can experience problems when upgrading:

Bugs

Bugs are unexpected side effects of code changes in the release, which cause problems. Some bugs occur for all users, and we usually catch these in the early stages of testing. Others occur in a small number of Grafana instances with specific configuration or unusual use cases; for example a specific authentication setup or a combination of feature toggles. Grafana plugins also interact with external services via API to query data, and sometimes these APIs change without notice, causing issues for your dashboards that depend on these datasources. Grafana Labs has monitoring in place to regularly test these APIs, but at times they break in unexpected ways.

Reduce the risk of bugs by staying current and rolling out upgrades across dev or test environments before production. A Grafana Enterprise license entitles you to an additional dev and test instance for this purpose, available through your account team, and in Grafana Cloud you can create dev and test stacks that upgrade before production by using rolling release channels.

• Back up your database on a regular basis, and especially before you upgrade.
• Roll back and report issues if you experience problems in dev or test.
• In Cloud, run a dev or test stack on the fast channel, and run your production stack on steady or slow. To change your release channel, open a support ticket.

Known breaking changes

As a rule we always seek backward compatibility and migration, and reserve breaking changes for Grafana’s once-yearly major release. However occasionally small breaking changes (like updates to API payloads) will ship in minor releases. These are announced in upgrade guides, What’s New, and our changelog.

Always read the upgrade guide and changelog prior to upgrading to learn about and account for breaking changes.

Plugin incompatibility

Grafana core ships as a single binary and consists of Dashboards, Alerts, Explore, Authentication and Authorization, Reporting, some core data sources, and other components. However, almost everyone who uses Grafana also uses plugins: panels, data sources, and applications that are released independently of Grafana. Every plugin version lists its Grafana version dependencies (you can see them at https://grafana.com/grafana/plugins/) but different versions of different plugins can also interact with each other - for example you might visualize data from a data source in a panel in Grafana, all three of which are versioned independently of each other. That can create issues that are hard to catch in testing.

To minimize the likelihood of plugin incompatibility issues, run the latest available version of plugins and update them regularly. Always update plugins before updating Grafana. Plugins also follow Semver patterns, so review the plugin’s changelog for breaking changes before upgrading to a new major version of that plugin.