<![CDATA[Syncthing - Package updates]]>This topic is to track Syncthing package updates.

Please open issues in a separate topic instead of replying here.

]]>https://forum.cloudron.io/topic/2446/syncthing-package-updatesRSS for NodeTue, 13 Oct 2026 04:12:38 GMTTue, 05 May 2020 10:53:03 GMT60<![CDATA[Reply to Syncthing - Package updates on Tue, 06 Oct 2026 15:48:37 GMT]]>[1.34.5]

  • Update syncthing to 2.1.6
  • Full Changelog
  • fix(model): introducers should not be able to add themselves to folders by @calmh in #10880
  • fix(gui): add accessible labels to buttons in Edit Device modal (fixes #10873) by @tomasz1986 in #10874
  • fix(model): properly error out when a temp file can't be created by @calmh in #10883
  • fix: disable keepalive on most outgoing HTTP connections by @calmh in #10891
  • fix(monitor): continue log writes when stdout is unavailable on detached Windows consoles (fixes #10882) by @Shablone in #10889
  • fix(gui): improve header and button color contrast (fixes #10488) by @giri256 in #10815
  • fix: use global short lived HTTP client with proper HTTP/2 support by @calmh in #10901
  • fix: remove unnecessary delay in index transmission by @calmh in #10908
  • fix(watchaggregator): properly convert floating-point time duration (fixes #10899) by @calmh in #10900
]]>https://forum.cloudron.io/post/130555https://forum.cloudron.io/post/130555Tue, 06 Oct 2026 15:48:37 GMT<![CDATA[Reply to Syncthing - Package updates on Wed, 09 Sep 2026 15:31:13 GMT]]>[1.34.4]

  • Update syncthing to 2.1.5
  • Full Changelog
  • Devices and folders can now be grouped in the GUI by setting the new group attribute.
  • HTTP and HTTPS proxies with support for CONNECT can now be used, in addition to the existing support for SOCKS proxies (the environment variable all_proxy=https://...).
  • Block indexing can be turned off for folders where it's more desirable to optimise for reduced database size and overhead than minimal transfer size (the blockIndexing attribute on folder configuration).
  • GUI login session duration can be configured to be longer or shorter than the default one week, or set to infinitely long. The cookie path can also be adjusted. (The sessionCookieDurationS and sessionCookiePath attributes in the GUI configuration.)
  • APT repository: https://apt.syncthing.net/
  • Full Changelog: https://github.com/syncthing/syncthing/compare/v2.1.4...v2.1.5
]]>https://forum.cloudron.io/post/129263https://forum.cloudron.io/post/129263Wed, 09 Sep 2026 15:31:13 GMT<![CDATA[Reply to Syncthing - Package updates on Thu, 06 Aug 2026 07:36:15 GMT]]>[1.34.3]

  • Update syncthing to 2.1.3
  • Full Changelog
  • fix(ignore, fs): allow loading ignore patterns behind symlink (fixes #10785) by @calmh in #10786
  • fix: avoid warning on does-not-exist scan error (fixes #10465) by @calmh in #10791
  • fix(strelaypoolsrv): locking correctness by @calmh in #10801
  • fix(model): properly health-check up-to-date folders (fixes #10546) by @calmh in #10773
  • fix(gui): fix expanding one folder not collapsing others in group by @tbodt in #10809
  • fix(gui): add bottom margin to folder action buttons for wrapped spacing by @rohitanwar in #10728
  • fix(upnp): guard against out of index string access by @calmh in #10834
  • fix(ignore): handle pattern resulting in empty string by @calmh in #10835
  • fix(versioner): handle invalid empty command by @calmh in #10836
  • fix(db, model): better handle db connections, puller concurrency, avoid deadlock (fixes #10841) by @calmh in #10842
]]>https://forum.cloudron.io/post/127784https://forum.cloudron.io/post/127784Thu, 06 Aug 2026 07:36:15 GMT<![CDATA[Reply to Syncthing - Package updates on Thu, 09 Jul 2026 09:07:18 GMT]]>[1.34.2]

  • Update syncthing to 2.1.2
  • Full Changelog
  • fix: on Windows don't allocate console if not opened inside one by @Shablone in #10726
  • fix(connections): do not report connection metrics for self (ref #10509) by @calmh in #10724
  • fix: let umask do the thing by @calmh in #10723
  • fix(fs, model): improve symlink resilience in file shortcut by @calmh in #10739
  • fix(protocol): always expect & validate block hash in requests by @calmh in #10738
  • fix(protocol): be more stringent about blocks in non-file entries by @calmh in #10737
  • fix(protocol): loosen restriction on size of directory entries by @calmh in #10743
  • fix(folder): check if context canceled when scanning (fixes #10363) by @henriksb1 in #10757
  • fix(config): remove extraneous defaults setting while unmarshalling folder options (fixes #10746, fixes #10389) by @calmh in #10763
  • fix(sqlite): update last migration to set schema version, counts by @calmh in #10768
]]>https://forum.cloudron.io/post/126580https://forum.cloudron.io/post/126580Thu, 09 Jul 2026 09:07:18 GMT<![CDATA[Reply to Syncthing - Package updates on Tue, 02 Jun 2026 17:22:02 GMT]]>[1.34.1]

  • Update syncthing to 2.1.1
  • Full Changelog
  • fix(syncthing): properly upgrade via REST when Syncthing is running (fixes #10697) by @calmh in #10699
  • fix(versioner): ensure user read/write/execute on archived dirs (fixes #10532) by @calmh in #10696
  • fix(discover): only announce wildcard for TCP punching when listening on wildcard address (fixes #10503) by @calmh in #10691
  • fix(stcrashreceiver): close source loader responses on errors by @mattn in #10704
  • fix(protocol): handle zero-size requests (fixes #10709) by @calmh in #10710
]]>https://forum.cloudron.io/post/125403https://forum.cloudron.io/post/125403Tue, 02 Jun 2026 17:22:02 GMT<![CDATA[Reply to Syncthing - Package updates on Tue, 12 May 2026 10:26:14 GMT]]>[1.34.0]

  • Update syncthing to 2.1.0
  • Full Changelog
  • fix(stdiscosrv): close file descriptor on flush error in write by @cuiweixie in #10615
  • fix(gui): disable autocomplete for folder password by @bt90 in #10342
  • fix(protocol): limit size of incoming request messages by @calmh in #10629
  • fix(gui): don't show local device under remote devices (ref #10563) by @maen-bn in #10631
  • fix(gui): order folders alphabetically and ensure local device stays hidden (ref #10563, ref #10631) by @maen-bn in #10637
  • fix(gui): fallback to folder ID when label is empty in remove dialog by @RealCharlesChia in #10657
  • fix(gui): fix tabs visually disabled but still clickable during ignore patterns setup (fixes #10634) by @JRNitre in #10651
  • fix(strelaysrv): properly use bind address for outgoing requests (fixes #10658) by @calmh in #10659
  • feat(gui, config): support simple folder grouping (fixes #2070) by @maen-bn in #10563
  • feat(dialer): add HTTP/HTTPS proxy support via CONNECT by @luizluca in #10572
]]>https://forum.cloudron.io/post/124617https://forum.cloudron.io/post/124617Tue, 12 May 2026 10:26:14 GMT<![CDATA[Reply to Syncthing - Package updates on Wed, 08 Apr 2026 08:44:35 GMT]]>[1.33.17]

  • Update syncthing to 2.0.16
  • Full Changelog
  • Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
  • The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per package, and a new log level WARNING has been inserted between INFO and ERROR (which was previously known as WARNING...). The INFO level has become more verbose, indicating the sync actions taken by Syncthing. A new command line flag --log-level sets the default log level for all packages, and the STTRACE environment variable and GUI has been updated to set log levels per package. The --verbose and --logflags command line options have been removed and will be ignored if given.
  • Deleted items are no longer kept forever in the database, instead they are forgotten after fifteen months. If your use case require deletes to take effect after more than a fifteen month delay, set the --db-delete-retention-interval command line option or corresponding environment variable to zero, or a longer time interval of your choosing.
  • Modernised command line options parsing. Old single-dash long options are no longer supported, e.g. -home must be given as --home. Some options have been renamed, others have become subcommands. All serve options are now also accepted as environment variables. See syncthing --help and syncthing serve --help for details.
  • Rolling hash detection of shifted data is no longer supported as this effectively never helped. Instead, scanning and syncing is faster and more efficient without it.
  • A "default folder" is no longer created on first startup.
  • Multiple connections are now used by default between v2 devices. The new default value is to use three connections: one for index metadata and two for data exchange.
  • The following platforms unfortunately no longer get prebuilt binaries for download at syncthing.net and on GitHub, due to complexities related to cross compilation with SQLite:
  • The handling of conflict resolution involving deleted files has changed. A delete can now be the winning outcome of conflict resolution, resulting in the deleted file being moved to a conflict copy.
  • fix(protocol): verify compressed message length before decompression by @​calmh in #​10595
]]>https://forum.cloudron.io/post/123044https://forum.cloudron.io/post/123044Wed, 08 Apr 2026 08:44:35 GMT<![CDATA[Reply to Syncthing - Package updates on Tue, 03 Mar 2026 12:35:00 GMT]]>[1.33.16]

  • Update syncthing to 2.0.15
  • Full Changelog
  • Database backend switched from LevelDB to SQLite. There is a migration on
  • first launch which can be lengthy for larger setups. The new database is
  • easier to understand and maintain and, hopefully, less buggy.
  • The logging format has changed to use structured log entries (a message
  • plus several key-value pairs). Additionally, we can now control the log
  • level per package, and a new log level WARNING has been inserted between
  • INFO and ERROR (which was previously known as WARNING...). The INFO level
  • has become more verbose, indicating the sync actions taken by Syncthing. A
  • new command line flag --log-level sets the default log level for all
  • packages, and the STTRACE environment variable and GUI has been updated
  • to set log levels per package. The --verbose and --logflags command
  • line options have been removed and will be ignored if given.
  • packages, and the STTRACE environment variable and GUI has been updated
]]>https://forum.cloudron.io/post/121154https://forum.cloudron.io/post/121154Tue, 03 Mar 2026 12:35:00 GMT<![CDATA[Reply to Syncthing - Package updates on Wed, 04 Feb 2026 07:33:33 GMT]]>[1.33.15]

]]>https://forum.cloudron.io/post/119624https://forum.cloudron.io/post/119624Wed, 04 Feb 2026 07:33:33 GMT<![CDATA[Reply to Syncthing - Package updates on Wed, 07 Jan 2026 09:03:33 GMT]]>[1.33.14]

  • Update syncthing to 2.0.13
  • Full Changelog
  • Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
  • The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per package, and a new log level WARNING has been inserted between INFO and ERROR (which was previously known as WARNING...). The INFO level has become more verbose, indicating the sync actions taken by Syncthing. A new command line flag --log-level sets the default log level for all packages, and the STTRACE environment variable and GUI has been updated to set log levels per package. The --verbose and --logflags command line options have been removed and will be ignored if given.
  • Deleted items are no longer kept forever in the database, instead they are forgotten after fifteen months. If your use case require deletes to take effect after more than a fifteen month delay, set the --db-delete-retention-interval command line option or corresponding environment variable to zero, or a longer time interval of your choosing.
  • Modernised command line options parsing. Old single-dash long options are no longer supported, e.g. -home must be given as --home. Some options have been renamed, others have become subcommands. All serve options are now also accepted as environment variables. See syncthing --help and syncthing serve --help for details.
  • Rolling hash detection of shifted data is no longer supported as this effectively never helped. Instead, scanning and syncing is faster and more efficient without it.
  • A "default folder" is no longer created on first startup.
  • Multiple connections are now used by default between v2 devices. The new default value is to use three connections: one for index metadata and two for data exchange.
  • The following platforms unfortunately no longer get prebuilt binaries for download at syncthing.net and on GitHub, due to complexities related to cross compilation with SQLite:
  • The handling of conflict resolution involving deleted files has changed. A delete can now be the winning outcome of conflict resolution, resulting in the deleted file being moved to a conflict copy.
  • fix(beacon): don't join multicast groups on non-multicast interfaces (fixes #10497) by @marbens-arch in #10498
]]>https://forum.cloudron.io/post/118056https://forum.cloudron.io/post/118056Wed, 07 Jan 2026 09:03:33 GMT<![CDATA[Reply to Syncthing - Package updates on Tue, 02 Dec 2025 09:21:45 GMT]]>[1.33.13]

  • Update syncthing to 2.0.12
  • Full Changelog
  • Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
  • The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per package, and a new log level WARNING has been inserted between INFO and ERROR (which was previously known as WARNING...). The INFO level has become more verbose, indicating the sync actions taken by Syncthing. A new command line flag --log-level sets the default log level for all packages, and the STTRACE environment variable and GUI has been updated to set log levels per package. The --verbose and --logflags command line options have been removed and will be ignored if given.
  • Deleted items are no longer kept forever in the database, instead they are forgotten after fifteen months. If your use case require deletes to take effect after more than a fifteen month delay, set the --db-delete-retention-interval command line option or corresponding environment variable to zero, or a longer time interval of your choosing.
  • Modernised command line options parsing. Old single-dash long options are no longer supported, e.g. -home must be given as --home. Some options have been renamed, others have become subcommands. All serve options are now also accepted as environment variables. See syncthing --help and syncthing serve --help for details.
  • Rolling hash detection of shifted data is no longer supported as this effectively never helped. Instead, scanning and syncing is faster and more efficient without it.
  • A "default folder" is no longer created on first startup.
  • Multiple connections are now used by default between v2 devices. The new default value is to use three connections: one for index metadata and two for data exchange.
  • The following platforms unfortunately no longer get prebuilt binaries for download at syncthing.net and on GitHub, due to complexities related to cross compilation with SQLite:
  • The handling of conflict resolution involving deleted files has changed. A delete can now be the winning outcome of conflict resolution, resulting in the deleted file being moved to a conflict copy.
]]>https://forum.cloudron.io/post/116342https://forum.cloudron.io/post/116342Tue, 02 Dec 2025 09:21:45 GMT<![CDATA[Reply to Syncthing - Package updates on Tue, 04 Nov 2025 12:21:27 GMT]]>[1.33.12]

  • Update syncthing to 2.0.11
  • Full Changelog
  • Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
  • The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per package, and a new log level WARNING has been inserted between INFO and ERROR (which was previously known as WARNING...). The INFO level has become more verbose, indicating the sync actions taken by Syncthing. A new command line flag --log-level sets the default log level for all packages, and the STTRACE environment variable and GUI has been updated to set log levels per package. The --verbose and --logflags command line options have been removed and will be ignored if given.
  • Deleted items are no longer kept forever in the database, instead they are forgotten after fifteen months. If your use case require deletes to take effect after more than a fifteen month delay, set the --db-delete-retention-interval command line option or corresponding environment variable to zero, or a longer time interval of your choosing.
  • Modernised command line options parsing. Old single-dash long options are no longer supported, e.g. -home must be given as --home. Some options have been renamed, others have become subcommands. All serve options are now also accepted as environment variables. See syncthing --help and syncthing serve --help for details.
  • Rolling hash detection of shifted data is no longer supported as this effectively never helped. Instead, scanning and syncing is faster and more efficient without it.
  • A "default folder" is no longer created on first startup.
  • Multiple connections are now used by default between v2 devices. The new default value is to use three connections: one for index metadata and two for data exchange.
  • The following platforms unfortunately no longer get prebuilt binaries for download at syncthing.net and on GitHub, due to complexities related to cross compilation with SQLite:
  • The handling of conflict resolution involving deleted files has changed. A delete can now be the winning outcome of conflict resolution, resulting in the deleted file being moved to a conflict copy.
  • fix(policy): only allow approvals by non-author contributors by @marbens-arch in #10419
  • fix(fs): store getExpireAdd mutex in caseCache (fixes #9836) by @marbens-arch in #10430
]]>https://forum.cloudron.io/post/114860https://forum.cloudron.io/post/114860Tue, 04 Nov 2025 12:21:27 GMT<![CDATA[Reply to Syncthing - Package updates on Wed, 24 Sep 2025 10:00:15 GMT]]>[1.33.11]

  • Update syncthing to 2.0.10
  • Full Changelog
  • Database backend switched from LevelDB to SQLite. There is a migration on
  • first launch which can be lengthy for larger setups. The new database is
  • easier to understand and maintain and, hopefully, less buggy.
  • The logging format has changed to use structured log entries (a message
  • plus several key-value pairs). Additionally, we can now control the log
  • level per package, and a new log level WARNING has been inserted between
  • INFO and ERROR (which was previously known as WARNING...). The INFO level
  • has become more verbose, indicating the sync actions taken by Syncthing. A
  • new command line flag --log-level sets the default log level for all
  • packages, and the STTRACE environment variable and GUI has been updated
  • to set log levels per package. The --verbose and --logflags command
  • line options have been removed and will be ignored if given.
  • Deleted items are no longer kept forever in the database, instead they are
  • forgotten after fifteen months. If your use case require deletes to take
  • effect after more than a fifteen month delay, set the
  • --db-delete-retention-interval command line option or corresponding
  • environment variable to zero, or a longer time interval of your choosing.
  • Modernised command line options parsing. Old single-dash long options are
  • no longer supported, e.g. -home must be given as --home. Some options
  • have been renamed, others have become subcommands. All serve options are
  • now also accepted as environment variables. See syncthing --help and
  • syncthing serve --help for details.
  • Rolling hash detection of shifted data is no longer supported as this
  • effectively never helped. Instead, scanning and syncing is faster and more
  • efficient without it.
  • A "default folder" is no longer created on first startup.
  • Multiple connections are now used by default between v2 devices. The new
  • default value is to use three connections: one for index metadata and two
  • for data exchange.
  • The following platforms unfortunately no longer get prebuilt binaries for
  • download at syncthing.net and on GitHub, due to complexities related to
  • cross compilation with SQLite:
  • fix: improve conflict detection by tracking previous file hash (fixes #​10349) by @​calmh in #​10351
]]>https://forum.cloudron.io/post/112933https://forum.cloudron.io/post/112933Wed, 24 Sep 2025 10:00:15 GMT<![CDATA[Reply to Syncthing - Package updates on Sat, 13 Sep 2025 15:05:41 GMT]]>[1.33.10]

  • Update syncthing to 2.0.9
  • Full Changelog
  • Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
  • The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per package, and a new log level WARNING has been inserted between INFO and ERROR (which was previously known as WARNING...). The INFO level has become more verbose, indicating the sync actions taken by Syncthing. A new command line flag --log-level sets the default log level for all packages, and the STTRACE environment variable and GUI has been updated to set log levels per package. The --verbose and --logflags command line options have been removed and will be ignored if given.
  • Deleted items are no longer kept forever in the database, instead they are forgotten after fifteen months. If your use case require deletes to take effect after more than a fifteen month delay, set the --db-delete-retention-interval command line option or corresponding environment variable to zero, or a longer time interval of your choosing.
  • Modernised command line options parsing. Old single-dash long options are no longer supported, e.g. -home must be given as --home. Some options have been renamed, others have become subcommands. All serve options are now also accepted as environment variables. See syncthing --help and syncthing serve --help for details.
  • Rolling hash detection of shifted data is no longer supported as this effectively never helped. Instead, scanning and syncing is faster and more efficient without it.
  • A "default folder" is no longer created on first startup.
  • Multiple connections are now used by default between v2 devices. The new default value is to use three connections: one for index metadata and two for data exchange.
  • The following platforms unfortunately no longer get prebuilt binaries for download at syncthing.net and on GitHub, due to complexities related to cross compilation with SQLite:
  • The handling of conflict resolution involving deleted files has changed. A delete can now be the winning outcome of conflict resolution, resulting in the deleted file being moved to a conflict copy.
  • fix(sqlite): add _txlock=immediate to modernc implementation by @calmh in #10384
  • fix(api): limit size of allowed authentication request by @calmh in #10386
]]>https://forum.cloudron.io/post/112661https://forum.cloudron.io/post/112661Sat, 13 Sep 2025 15:05:41 GMT<![CDATA[Reply to Syncthing - Package updates on Mon, 08 Sep 2025 14:08:41 GMT]]>[1.33.9]

  • Update syncthing to 2.0.8
  • Full Changelog
  • Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
  • The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per package, and a new log level WARNING has been inserted between INFO and ERROR (which was previously known as WARNING...). The INFO level has become more verbose, indicating the sync actions taken by Syncthing. A new command line flag --log-level sets the default log level for all packages, and the STTRACE environment variable and GUI has been updated to set log levels per package. The --verbose and --logflags command line options have been removed and will be ignored if given.
  • Deleted items are no longer kept forever in the database, instead they are forgotten after fifteen months. If your use case require deletes to take effect after more than a fifteen month delay, set the --db-delete-retention-interval command line option or corresponding environment variable to zero, or a longer time interval of your choosing.
  • Modernised command line options parsing. Old single-dash long options are no longer supported, e.g. -home must be given as --home. Some options have been renamed, others have become subcommands. All serve options are now also accepted as environment variables. See syncthing --help and syncthing serve --help for details.
  • Rolling hash detection of shifted data is no longer supported as this effectively never helped. Instead, scanning and syncing is faster and more efficient without it.
  • A "default folder" is no longer created on first startup.
  • Multiple connections are now used by default between v2 devices. The new default value is to use three connections: one for index metadata and two for data exchange.
  • The following platforms unfortunately no longer get prebuilt binaries for download at syncthing.net and on GitHub, due to complexities related to cross compilation with SQLite:
  • The handling of conflict resolution involving deleted files has changed. A delete can now be the winning outcome of conflict resolution, resulting in the deleted file being moved to a conflict copy.
  • fix(sqlite): less impactful periodic garbage collection by @calmh in #10374
  • fix(sqlite): explicitly set temporary directory location (fixes #10368) by @calmh in #10376
]]>https://forum.cloudron.io/post/112498https://forum.cloudron.io/post/112498Mon, 08 Sep 2025 14:08:41 GMT<![CDATA[Reply to Syncthing - Package updates on Sat, 06 Sep 2025 08:09:39 GMT]]>[1.33.8]

  • Update syncthing to 2.0.7
  • Full Changelog
  • Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
  • The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per package, and a new log level WARNING has been inserted between INFO and ERROR (which was previously known as WARNING...). The INFO level has become more verbose, indicating the sync actions taken by Syncthing. A new command line flag --log-level sets the default log level for all packages, and the STTRACE environment variable and GUI has been updated to set log levels per package. The --verbose and --logflags command line options have been removed and will be ignored if given.
  • Deleted items are no longer kept forever in the database, instead they are forgotten after fifteen months. If your use case require deletes to take effect after more than a fifteen month delay, set the --db-delete-retention-interval command line option or corresponding environment variable to zero, or a longer time interval of your choosing.
  • Modernised command line options parsing. Old single-dash long options are no longer supported, e.g. -home must be given as --home. Some options have been renamed, others have become subcommands. All serve options are now also accepted as environment variables. See syncthing --help and syncthing serve --help for details.
  • Rolling hash detection of shifted data is no longer supported as this effectively never helped. Instead, scanning and syncing is faster and more efficient without it.
  • A "default folder" is no longer created on first startup.
  • Multiple connections are now used by default between v2 devices. The new default value is to use three connections: one for index metadata and two for data exchange.
  • The following platforms unfortunately no longer get prebuilt binaries for download at syncthing.net and on GitHub, due to complexities related to cross compilation with SQLite:
  • The handling of conflict resolution involving deleted files has changed. A delete can now be the winning outcome of conflict resolution, resulting in the deleted file being moved to a conflict copy.
  • fix(model): earlier free-space check (fixes #10347) by @calmh in #10348
  • fix(api): redact device encryption passwords in support bundle config by @pixelspark in #10359
]]>https://forum.cloudron.io/post/112443https://forum.cloudron.io/post/112443Sat, 06 Sep 2025 08:09:39 GMT<![CDATA[Reply to Syncthing - Package updates on Thu, 04 Sep 2025 07:30:44 GMT]]>[1.33.7]

  • Update syncthing to 2.0.6
  • Full Changelog
  • Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
  • The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per package, and a new log level WARNING has been inserted between INFO and ERROR (which was previously known as WARNING...). The INFO level has become more verbose, indicating the sync actions taken by Syncthing. A new command line flag --log-level sets the default log level for all packages, and the STTRACE environment variable and GUI has been updated to set log levels per package. The --verbose and --logflags command line options have been removed and will be ignored if given.
  • Deleted items are no longer kept forever in the database, instead they are forgotten after fifteen months. If your use case require deletes to take effect after more than a fifteen month delay, set the --db-delete-retention-interval command line option or corresponding environment variable to zero, or a longer time interval of your choosing.
  • Modernised command line options parsing. Old single-dash long options are no longer supported, e.g. -home must be given as --home. Some options have been renamed, others have become subcommands. All serve options are now also accepted as environment variables. See syncthing --help and syncthing serve --help for details.
  • Rolling hash detection of shifted data is no longer supported as this effectively never helped. Instead, scanning and syncing is faster and more efficient without it.
  • A "default folder" is no longer created on first startup.
  • Multiple connections are now used by default between v2 devices. The new default value is to use three connections: one for index metadata and two for data exchange.
  • The following platforms unfortunately no longer get prebuilt binaries for download at syncthing.net and on GitHub, due to complexities related to cross compilation with SQLite:
  • The handling of conflict resolution involving deleted files has changed. A delete can now be the winning outcome of conflict resolution, resulting in the deleted file being moved to a conflict copy.
  • fix(db): remove temp_store = MEMORY pragmas by @calmh in #10343
]]>https://forum.cloudron.io/post/112373https://forum.cloudron.io/post/112373Thu, 04 Sep 2025 07:30:44 GMT<![CDATA[Reply to Syncthing - Package updates on Wed, 03 Sep 2025 06:46:54 GMT]]>[1.33.6]

  • Update syncthing to 2.0.5
  • Full Changelog
  • Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
  • The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per package, and a new log level WARNING has been inserted between INFO and ERROR (which was previously known as WARNING...). The INFO level has become more verbose, indicating the sync actions taken by Syncthing. A new command line flag --log-level sets the default log level for all packages, and the STTRACE environment variable and GUI has been updated to set log levels per package. The --verbose and --logflags command line options have been removed and will be ignored if given.
  • Deleted items are no longer kept forever in the database, instead they are forgotten after fifteen months. If your use case require deletes to take effect after more than a fifteen month delay, set the --db-delete-retention-interval command line option or corresponding environment variable to zero, or a longer time interval of your choosing.
  • Modernised command line options parsing. Old single-dash long options are no longer supported, e.g. -home must be given as --home. Some options have been renamed, others have become subcommands. All serve options are now also accepted as environment variables. See syncthing --help and syncthing serve --help for details.
  • Rolling hash detection of shifted data is no longer supported as this effectively never helped. Instead, scanning and syncing is faster and more efficient without it.
  • A "default folder" is no longer created on first startup.
  • Multiple connections are now used by default between v2 devices. The new default value is to use three connections: one for index metadata and two for data exchange.
  • The following platforms unfortunately no longer get prebuilt binaries for download at syncthing.net and on GitHub, due to complexities related to cross compilation with SQLite:
  • The handling of conflict resolution involving deleted files has changed. A delete can now be the winning outcome of conflict resolution, resulting in the deleted file being moved to a conflict copy.
  • fix(db): only vacuum database on startup when a migration script was actually run by @pixelspark in https://github.com/syncthing/syncthing/pull/10339
]]>https://forum.cloudron.io/post/112321https://forum.cloudron.io/post/112321Wed, 03 Sep 2025 06:46:54 GMT<![CDATA[Reply to Syncthing - Package updates on Tue, 02 Sep 2025 07:47:41 GMT]]>[1.33.5]

]]>https://forum.cloudron.io/post/112288https://forum.cloudron.io/post/112288Tue, 02 Sep 2025 07:47:41 GMT<![CDATA[Reply to Syncthing - Package updates on Sat, 23 Aug 2025 06:41:27 GMT]]>[1.33.4]

  • Update syncthing to 2.0.3
  • Full Changelog
  • Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
  • The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per package, and a new log level WARNING has been inserted between INFO and ERROR (which was previously known as WARNING...). The INFO level has become more verbose, indicating the sync actions taken by Syncthing. A new command line flag --log-level sets the default log level for all packages, and the STTRACE environment variable and GUI has been updated to set log levels per package. The --verbose and --logflags command line options have been removed and will be ignored if given.
  • Deleted items are no longer kept forever in the database, instead they are forgotten after fifteen months. If your use case require deletes to take effect after more than a fifteen month delay, set the --db-delete-retention-interval command line option or corresponding environment variable to zero, or a longer time interval of your choosing.
  • Modernised command line options parsing. Old single-dash long options are no longer supported, e.g. -home must be given as --home. Some options have been renamed, others have become subcommands. All serve options are now also accepted as environment variables. See syncthing --help and syncthing serve --help for details.
  • Rolling hash detection of shifted data is no longer supported as this effectively never helped. Instead, scanning and syncing is faster and more efficient without it.
  • A "default folder" is no longer created on first startup.
  • Multiple connections are now used by default between v2 devices. The new default value is to use three connections: one for index metadata and two for data exchange.
  • The following platforms unfortunately no longer get prebuilt binaries for download at syncthing.net and on GitHub, due to complexities related to cross compilation with SQLite:
  • The handling of conflict resolution involving deleted files has changed. A delete can now be the winning outcome of conflict resolution, resulting in the deleted file being moved to a conflict copy.
  • fix(cmd): restore --version flag for compatibility by @acolomb in https://github.com/syncthing/syncthing/pull/10269
]]>https://forum.cloudron.io/post/111941https://forum.cloudron.io/post/111941Sat, 23 Aug 2025 06:41:27 GMT<![CDATA[Reply to Syncthing - Package updates on Mon, 18 Aug 2025 16:24:54 GMT]]>[1.33.3]

  • Fix checklist
]]>https://forum.cloudron.io/post/111785https://forum.cloudron.io/post/111785Mon, 18 Aug 2025 16:24:54 GMT<![CDATA[Reply to Syncthing - Package updates on Sat, 16 Aug 2025 08:17:21 GMT]]>[1.32.2]

  • Update syncthing to 2.0.2
  • Full Changelog
  • Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
  • The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per package, and a new log level WARNING has been inserted between INFO and ERROR (which was previously known as WARNING...). The INFO level has become more verbose, indicating the sync actions taken by Syncthing. A new command line flag --log-level sets the default log level for all packages, and the STTRACE environment variable and GUI has been updated to set log levels per package. The --verbose and --logflags command line options have been removed and will be ignored if given.
  • Deleted items are no longer kept forever in the database, instead they are forgotten after fifteen months. If your use case require deletes to take effect after more than a fifteen month delay, set the --db-delete-retention-interval command line option or corresponding environment variable to zero, or a longer time interval of your choosing.
  • Modernised command line options parsing. Old single-dash long options are no longer supported, e.g. -home must be given as --home. Some options have been renamed, others have become subcommands. All serve options are now also accepted as environment variables. See syncthing --help and syncthing serve --help for details.
  • Rolling hash detection of shifted data is no longer supported as this effectively never helped. Instead, scanning and syncing is faster and more efficient without it.
  • A "default folder" is no longer created on first startup.
  • Multiple connections are now used by default between v2 devices. The new default value is to use three connections: one for index metadata and two for data exchange.
  • The following platforms unfortunately no longer get prebuilt binaries for download at syncthing.net and on GitHub, due to complexities related to cross compilation with SQLite:
  • The handling of conflict resolution involving deleted files has changed. A delete can now be the winning outcome of conflict resolution, resulting in the deleted file being moved to a conflict copy.
  • build: remove netgo and osusergo build tags (fixes #10251) by @calmh in https://github.com/syncthing/syncthing/pull/10256
]]>https://forum.cloudron.io/post/111668https://forum.cloudron.io/post/111668Sat, 16 Aug 2025 08:17:21 GMT<![CDATA[Reply to Syncthing - Package updates on Fri, 15 Aug 2025 08:35:42 GMT]]>[1.32.1]

]]>https://forum.cloudron.io/post/111612https://forum.cloudron.io/post/111612Fri, 15 Aug 2025 08:35:42 GMT<![CDATA[Reply to Syncthing - Package updates on Tue, 12 Aug 2025 12:54:22 GMT]]>[1.32.0]

  • Update syncthing to 2.0.0
  • Full Changelog
  • Database backend switched from LevelDB to SQLite. There is a migration on first launch which can be lengthy for larger setups. The new database is easier to understand and maintain and, hopefully, less buggy.
  • The logging format has changed to use structured log entries (a message plus several key-value pairs). Additionally, we can now control the log level per package, and a new log level WARNING has been inserted between INFO and ERROR (which was previously known as WARNING...). The INFO level has become more verbose, indicating the sync actions taken by Syncthing. A new command line flag --log-level sets the default log level for all packages, and the STTRACE environment variable and GUI has been updated to set log levels per package. The --verbose and --logflags command line options have been removed and will be ignored if given.
  • Deleted items are no longer kept forever in the database, instead they are forgotten after six months. If your use case require deletes to take effect after more than a six month delay, set the --db-delete-retention-interval command line option or corresponding environment variable to zero, or a longer time interval of your choosing.
  • Modernised command line options parsing. Old single-dash long options are no longer supported, e.g. -home must be given as --home. Some options have been renamed, others have become subcommands. All serve options are now also accepted as environment variables. See syncthing --help and syncthing serve --help for details.
  • Rolling hash detection of shifted data is no longer supported as this effectively never helped. Instead, scanning and syncing is faster and more efficient without it.
  • A "default folder" is no longer created on first startup.
  • Multiple connections are now used by default between v2 devices. The new default value is to use three connections: one for index metadata and two for data exchange.
  • The following platforms unfortunately no longer get prebuilt binaries for download at syncthing.net and on GitHub, due to complexities related to cross compilation with SQLite:
  • fix(db): handle large numbers of blocks in update by @calmh in https://github.com/syncthing/syncthing/pull/10025
  • fix(syncthing): make directory flags global for all commands by @calmh in https://github.com/syncthing/syncthing/pull/10028
]]>https://forum.cloudron.io/post/111500https://forum.cloudron.io/post/111500Tue, 12 Aug 2025 12:54:22 GMT