Clarifications on Grafana Release/Support lifecycle

(Writing this on behalf of, where we track grafana at /grafana).

Prior discussions on this forum have confirmed a “2 major releases supported” policy. However, we noticed today that:

  • 9.3.0, and 9.2.7 were released, but 8.5.16 is still pending
  • 9.3 seems to be getting feature fixes, while 9.2 is only getting bug fixes.


  1. Is v8 still supported?
  2. What kind of fixes are backported to prior major versions? Just security/critical bug-fixes/…?
  3. Is there a separate support cycle for minor releases now that 9.2 and 9.3 are being maintained differently? (In other words: Should we be showing 9.2 and 9.3 separately at
  4. Can the support policy be documented somewhere please? We have a nice set of recommendations at that might be helpful.

Prior discussions:

I checked recent security release
// Sorry I can not use several links because of my rank

Release 9.3.0, latest release with security patch:
Release 9.2.7, last 9.2 patch with security fix:

Stored XSS in Grafana Alerting (CVE-2022-31097)
Impacted versions
9.1.0-beta1 → 9.3.0-beta1

2022-11-28 11:47 PRs submitted for fix with backports to 9.1 and 9.2

From : ttps://

Maybe 9.1.x is released soon ??
Since this vulnerability is a regression, 8.5.x will not be released.

Release 9.2.4, latest patch, also containing security fix:
Release 8.5.15, only containing security fix:

From : ttps://

9.1.x seemed not released
Latest minor version of last 2 major versions are supported ??

Release 9.2, latest release with security fi
Release 9.1.8, only containing security fix
Release 8.5.14, only containing security fix

From :ttps://

(upstream 9.2 and) latest minor version of last 2 major versions are supported ??

We are also releasing security releases for Grafana 9.0.8, 8.5.11, 8.4.11 and 8.3.11

From : ttps://

Many backport relese …

I can’t understand backport support policy

Got an update on Slack. Re-posting here as the Slack needs a login:

  1. yes, we support the current minor (e.g. 9.3.x), the previous minor (e.g. 9.2.x) and the last minor of the previous major (e.g. 8.5.x)
  2. yes, mostly just security+critical bug fixes.
  3. current minor has full support, previous minor (e.g. 9.2.x) is similar to v8 in that it will only really receive security/critical fixes
  4. i’ve asked internally if we can get this published as i agree it’s valuable :slightly_smiling_face:


Slack Ref: Slack.

Slack Signup:

For the record: release policy - Grafana releases: New 2023 release schedule | Grafana Labs

Included the new release schedule in our page: Grafana | (Preview, PR is here).

But this only covers the release schedule, not the support policy - would be nice to have a stable page that covers both. A blog is not ideal, since blogs can get outdated (Kinda what happened with Grafana, where old forum posts referencing the old support policy were outdated).

Hi can I check is there official documentation or page which tell us about the support policy for Grafana OSS version? as my understanding is that only grafana enterprise have such policy of version n-1 will be supported, is that apply same to grafana OSS?

From my understanding (of documenting and writing up Grafana |, the support policy applies to Grafana OSS.

@captn3m0 Hi :slight_smile: Sorry for the slightly off-topic question, but how do you update the in your repository? I noticed that it still shows 9.4.3 as the latest release while we are already at 9.4.7 right now.

It auto-updates using the git tags on the grafana repo. Our automation has picked up the tag, but it hasn’t updated the markdown data.

Seems like a bug in our code somewhere - will check and update. Thanks for notifying!

The issue was with the 9.4.0 tag which was created after the 9.4.7 release.

"9.4.7": "2023-03-16"
"9.4.0": "2023-03-21"

Our automation finds a newer release (9.4.0, 21st March) with a lower version number than what’s current (9.4.3), and decides to not change anything since lowering a version number always a bad idea.

I’ve filed a PR to correct this for now: [grafana] Manually update to 9.4.7 by captn3m0 · Pull Request #2841 · endoflife-date/ · GitHub

I’m unsure why the 9.4.0 tag was created so late. If this was meant as a pre-tag, perhaps it could have been tagged as v9.4.0-pre on the actual date (2023-02-03)

Ah, that explains it, thanks :slightly_smiling_face:

Regarding 9.4.0 released after 9.4.7:

We had already created the 9.4.0 release internally when we had to redo it due to some critical issues. This led to us skipping 9.4.0 in the public release and going with 9.4.2 (IIRC) as the first public release for the 9.4.x series.

Unfortunately, that lack of a public 9.4.0 release caused some administrative issues not under our control and so - after learning about them - we decided to push 9.4.0 out. Sorry that this has caused some troubles for you :frowning_face:

1 Like