<?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 Homepage?</title>
    <link>https://bumplog.org/apps/homepage/</link>
    <description>Update-safety verdicts for Homepage (gethomepage/homepage), traceable to the GitHub release.</description>
    <language>en</language>
    <atom:link href="https://bumplog.org/apps/homepage/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Homepage v1.13.2 — Safe to update</title>
      <link>https://bumplog.org/apps/homepage/</link>
      <guid isPermaLink="false">bumplog:app:homepage:v1.13.2:safe</guid>
      <pubDate>Sun, 05 Jul 2026 00:00:00 GMT</pubDate>
      <description>Safe to update. The release notes contain no breaking changes, required migrations, or manual upgrade steps. All three fixes are narrow widget/integration corrections that improve correctness without altering configuration or behavior for unaffected users. Dependency updates are routine and internal to the build. What changed: v1.13.2 is a maintenance-focused release with three bug fixes: compatibility with the Dispatcharr v24 API, the ability to explicitly overwrite cookie headers, and a correction to the Seerr widget that was incorrectly injecting an &apos;available&apos; field. The remainder of the release consists entirely of dependency bumps and CI/tooling housekeeping, with no new user-facing features introduced. Source release: https://github.com/gethomepage/homepage/releases/tag/v1.13.2</description>
    </item>
  </channel>
</rss>
