<?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 Syncthing?</title>
    <link>https://bumplog.org/apps/syncthing/</link>
    <description>Update-safety verdicts for Syncthing (syncthing/syncthing), traceable to the GitHub release.</description>
    <language>en</language>
    <atom:link href="https://bumplog.org/apps/syncthing/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Syncthing v2.1.1 — Safe to update</title>
      <link>https://bumplog.org/apps/syncthing/</link>
      <guid isPermaLink="false">bumplog:app:syncthing:v2.1.1:safe</guid>
      <pubDate>Fri, 03 Jul 2026 00:00:00 GMT</pubDate>
      <description>Safe to update. The release notes list only bug fixes and internal build/chore changes with no mention of breaking changes, required migrations, or manual upgrade steps. The new 2.1 features (grouping, proxy support, block indexing toggle, session cookie config) are additive and opt-in, requiring no action from existing users. What changed: v2.1.1 is a patch release that ships several bug fixes on top of the 2.1 feature base. Fixes include a broken REST-based upgrade path when Syncthing is running, incorrect permissions on versioner-archived directories, a mis-announced wildcard address in TCP hole-punching discovery, and a crash on zero-size protocol requests. The 2.1 series also introduced device/folder grouping in the GUI, HTTP/HTTPS CONNECT proxy support, an option to disable block indexing per folder to reduce database overhead, and configurable GUI session cookie duration and path. Source release: https://github.com/syncthing/syncthing/releases/tag/v2.1.1</description>
    </item>
  </channel>
</rss>
