<?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 Grocy?</title>
    <link>https://bumplog.org/apps/grocy/</link>
    <description>Update-safety verdicts for Grocy (grocy/grocy), traceable to the GitHub release.</description>
    <language>en</language>
    <atom:link href="https://bumplog.org/apps/grocy/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Grocy v4.6.0 — Holds breaking changes</title>
      <link>https://bumplog.org/apps/grocy/</link>
      <guid isPermaLink="false">bumplog:app:grocy:v4.6.0:breaking</guid>
      <pubDate>Fri, 17 Jul 2026 00:00:00 GMT</pubDate>
      <description>Holds breaking changes. The release notes explicitly flag (with a ⚠️ warning) that PHP 8.5 with SQLite 3.40+ is now the only supported runtime, making this a hard infrastructure prerequisite. Self-hosters running any earlier PHP version must upgrade their runtime before updating Grocy, constituting a required manual upgrade step. All other changes in the release are additive features or bug fixes with no additional migration notes. What changed: v4.6.0 raises the minimum runtime to PHP 8.5 with SQLite 3.40+, dropping support for all earlier PHP versions. On the stock side, quantity-unit handling is significantly improved — units can now be freely changed before a product ever enters stock, and missing 1:1 conversions are auto-created, which streamlines barcode-lookup plugin workflows. A handful of long-standing bugs are fixed across stock, shopping lists, chores, userfields, and the date-shorthand input parser. FreeBSD users on SQLite 3.41+ also receive a targeted SQL workaround. Source release: https://github.com/grocy/grocy/releases/tag/v4.6.0</description>
    </item>
  </channel>
</rss>
