<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bumplog — is it safe to update Grafana?</title>
    <link>https://bumplog.org/apps/grafana/</link>
    <description>Update-safety verdicts for Grafana (grafana/grafana), traceable to the GitHub release.</description>
    <language>en</language>
    <atom:link href="https://bumplog.org/apps/grafana/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Grafana v13.0.3 — Safe to update</title>
      <link>https://bumplog.org/apps/grafana/</link>
      <guid isPermaLink="false">bumplog:app:grafana:v13.0.3:safe</guid>
      <pubDate>Wed, 01 Jul 2026 00:00:00 GMT</pubDate>
      <description>Safe to update. The release notes list only bug fixes and minor enhancements with no breaking changes, required migrations, or manual upgrade steps called out. The MySQL migration query fix is notable but is described as a bug fix, implying it corrects an existing fault rather than introducing a schema change requiring action. No deprecations or behavioral changes are flagged. What changed: v13.0.3 is a patch release focused on provisioning reliability and bug fixes. Docker images based on Alpine are bumped to a newer base version. Provisioning now correctly writes folder metadata files when dashboards are created in or moved into new folders, and several provisioning edge cases are resolved including multi-org PR comment handling and folder-rename link tracking. A bad MySQL query in a datasource type column migration is fixed, and the datasources API now correctly rejects mismatched UIDs with a 400 error. Source release: https://github.com/grafana/grafana/releases/tag/v13.0.3</description>
    </item>
  </channel>
</rss>
