Grafana 13.1.1

So Grafana 13.1.1 just dropped and I have been poking at it all morning. TL;DR: it is a patch release that fixes some annoying provisioning headaches — especially if you have been fighting with GitHub webhooks in your Grafana setup. Let us get into it.

What is Actually New

Not a huge release — it is a patch, after all — but there are a few quality-of-life improvements worth talking about:

• Go got bumped to 1.26.5 — Under the hood performance and security improvements from the Go runtime. You love to see it. (#128015)
• GitHub provisioning form errors got better — If you have ever stared at a cryptic connection failed message while setting up GitHub integrations, this one is for you. Error messages are actually useful now. (#128177)
• Per-resource write timeout — Provisioning sync now supports configurable write timeouts per resource. Big win if you are managing large-scale Grafana setups with slow API responses. (#127868)

Bug Fixes That Actually Matter

Three fixes that stood out to me:

• InlineToast accessibility — Screen readers now actually announce InlineToast content. Accessibility win. (#128687)
• Chained dashboard datasource panels — Fixed a nasty bug where chained dashboard datasource panels were showing stale data. If your dashboards reference other dashboards, this was probably driving you nuts. (#127248)
• GitHub webhook idempotency — Repos stuck showing unhealthy with HTTP 422 errors? Fixed. GitHub webhook creation is now idempotent, so you do not get duplicate webhooks bombing your repos. (#128201)

Should You Upgrade?

If you are using GitHub provisioning in Grafana, the answer is yes — update now. The webhook fix alone is worth it. If you are just running dashboards and alerts, 13.1.1 is a low-risk patch that keeps you current. No breaking changes, no migration drama.

Upgrade via your package manager or grab the binaries from the Grafana downloads page. Go on, you know you want to. 🔧