<?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 Miniflux?</title>
    <link>https://bumplog.org/apps/miniflux/</link>
    <description>Update-safety verdicts for Miniflux (miniflux/v2), traceable to the GitHub release.</description>
    <language>en</language>
    <atom:link href="https://bumplog.org/apps/miniflux/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Miniflux 2.3.2 — Update with care</title>
      <link>https://bumplog.org/apps/miniflux/</link>
      <guid isPermaLink="false">bumplog:app:miniflux:2.3.2:caution</guid>
      <pubDate>Mon, 13 Jul 2026 00:00:00 GMT</pubDate>
      <description>Update with care. The FIPS-mode fix replaces MD5 with SHA-256 for enclosure uniqueness and explicitly raises the minimum supported PostgreSQL version to 11; anyone on PostgreSQL 10 or below must upgrade their database first. All other changes are additive features, performance improvements, or bug fixes with no stated migration steps. What changed: Miniflux 2.3.2 delivers a meaningful search upgrade — full-text queries now support quoted phrases, OR operators, and negation via PostgreSQL&apos;s websearch_to_tsquery. The API gains new endpoints for paginated entry ID retrieval, bulk starring, and tag-based filtering. On the security side, login timing differences that could leak valid usernames are patched, and FIPS-mode PostgreSQL installations are now supported via SHA-256 instead of MD5 — though this raises the minimum required PostgreSQL version to 11. A broad set of bug fixes addresses enclosure proxying, nil pointer dereferences, API error codes, and localization formatting. Source release: https://github.com/miniflux/v2/releases/tag/2.3.2</description>
    </item>
  </channel>
</rss>
