<![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 NodeSun, 08 Mar 2026 03:25:45 GMTTue, 05 May 2020 10:53:03 GMT60<![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<![CDATA[Reply to Syncthing - Package updates on Wed, 30 Jul 2025 10:20:54 GMT]]>[1.31.0]

  • checklist added to manifest
]]>https://forum.cloudron.io/post/111009https://forum.cloudron.io/post/111009Wed, 30 Jul 2025 10:20:54 GMT<![CDATA[Reply to Syncthing - Package updates on Wed, 02 Jul 2025 07:11:25 GMT]]>[1.30.0]

]]>https://forum.cloudron.io/post/109574https://forum.cloudron.io/post/109574Wed, 02 Jul 2025 07:11:25 GMT<![CDATA[Reply to Syncthing - Package updates on Fri, 06 Sep 2024 09:44:02 GMT]]>[1.26.10]

]]>https://forum.cloudron.io/post/93948https://forum.cloudron.io/post/93948Fri, 06 Sep 2024 09:44:02 GMT<![CDATA[Reply to Syncthing - Package updates on Tue, 03 Sep 2024 15:19:08 GMT]]>[1.26.9]

]]>https://forum.cloudron.io/post/93801https://forum.cloudron.io/post/93801Tue, 03 Sep 2024 15:19:08 GMT<![CDATA[Reply to Syncthing - Package updates on Tue, 02 Jul 2024 12:34:49 GMT]]>[1.26.8]

]]>https://forum.cloudron.io/post/90760https://forum.cloudron.io/post/90760Tue, 02 Jul 2024 12:34:49 GMT<![CDATA[Reply to Syncthing - Package updates on Tue, 04 Jun 2024 14:44:17 GMT]]>[1.26.7]

  • Update Syncthing to 1.27.8
  • Full changelog
  • #9506: gui: Favicon not working in Firefox bookmarks
  • #9527: Device connection state metric
]]>https://forum.cloudron.io/post/89436https://forum.cloudron.io/post/89436Tue, 04 Jun 2024 14:44:17 GMT<![CDATA[Reply to Syncthing - Package updates on Wed, 08 May 2024 11:43:41 GMT]]>[1.26.6]

  • Update Syncthing to 1.27.7
  • Full changelog
  • #9503: lib/nat: panic: runtime error: index out of range
]]>https://forum.cloudron.io/post/88187https://forum.cloudron.io/post/88187Wed, 08 May 2024 11:43:41 GMT