Syncthing 2.1.7: eight fixes, clean upgrade from 2.1.6
Summary
Syncthing 2.1.7 is a bug-fix release built with Go 1.27.3. The release notes list eight fixes. They cover the SQLite database, global discovery announcements, protocol error handling and file sync logic in the model. The release also adds validation of incoming protocol messages with sensible size limits.
Breaking changes and deprecations
None listed in the release notes. We saw no changes to configuration or the web UI during the upgrade.
Tested in our lab
We installed 2.1.6 from the official release tarball and ran it as a systemd service. We added one send-receive folder with five random 200 KB files and waited for it to reach “idle”. We then stopped the service, replaced the binary with 2.1.7, and started it again.
- The service came back up and reported
v2.1.7. - The web UI answered with HTTP 200.
- The folder state was
idlewith 5 of 5 files, and no rescan problems appeared. - All five files matched their checksums from before the upgrade.
- The log had no new warnings or errors. The only warning was the usual “should not run as a privileged user” notice, which we also saw on 2.1.6.
Limits of this test: it was one device with no remote peers. Most of the fixes (receive-only reconciliation, parent ownership, recv-enc files, discovery retry-after) need specific setups, and we did not exercise them.
Note: Syncthing’s built-in auto-upgrade is on by default. On our first start of 2.1.6 it replaced itself with 2.1.7 within a second. We discarded that run and redid the test with STNOUPGRADE=1 set so the upgrade was a deliberate step on a populated database.
Lab log
$ syncthing --version
syncthing v2.1.6 "Hafnium Hornet" (go1.27.1 linux-amd64) builder@github.syncthing.net 2026-10-05 04:03:55 UTC
[...]
$ systemctl stop syncthing
$ syncthing --version
syncthing v2.1.7 "Hafnium Hornet" (go1.27.3 linux-amd64) builder@github.syncthing.net 2026-10-20 19:54:38 UTC
$ systemctl start syncthing
$ systemctl is-active syncthing
active
$ curl -s -H "X-API-Key: [redacted]" http://127.0.0.1:8384/rest/system/version | grep "\"version\""
"version": "v2.1.7"
$ curl -s -H "X-API-Key: [redacted]" "http://127.0.0.1:8384/rest/db/status?folder=testf" | grep -E "\"(globalFiles|state|localFiles)\""
"globalFiles": 5,
"localFiles": 5,
"state": "idle",
$ curl -s -o /dev/null -w "gui %{http_code}\n" http://127.0.0.1:8384/
gui 200
$ sha256sum -c /root/before.sha
f1.bin: OK
f2.bin: OK
f3.bin: OK
f4.bin: OK
f5.bin: OK
Reported by others
Nothing beyond the release notes. They reference issues #10913, #10924, #10928 and #8399 (parent ownership). See the release page. We did not review those issues.
Verdict
Upgrade when convenient. If you use receive-only folders or rely on file ownership syncing, the fixes may matter to you. The upgrade was uneventful in our lab. If you have auto-upgrade on, you may already be running it.