v2.0.8-ls195

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.8-ls195/index.html

LinuxServer Changes:

Rebase to Alpine 3.22.

Remote Changes:

Major changes in 2.0

• 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:

  • dragonfly/amd64
  • solaris/amd64
  • linux/ppc64
  • netbsd/*
  • openbsd/386 and openbsd/arm
  • windows/arm

• 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.

This release is also available as:

• APT repository: https://apt.syncthing.net/

• Docker image: docker.io/syncthing/syncthing:2.0.8 or ghcr.io/syncthing/syncthing:2.0.8
  ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

• fix(sqlite): less impactful periodic garbage collection by @calmh in syncthing/syncthing#10374
• fix(sqlite): explicitly set temporary directory location (fixes #10368) by @calmh in syncthing/syncthing#10376

Other

• build: trigger nightly build only on syncthing repo by @aminvakil in syncthing/syncthing#10375
• chore(scanner): always return values to the pools when hashing blocks by @imsodin in syncthing/syncthing#10377
• chore(sqlite): skip database GC entirely when it's provably unnecessary by @calmh in syncthing/syncthing#10379

New Contributors

• @aminvakil made their first contribution in syncthing/syncthing#10375

Full Changelog: syncthing/syncthing@v2.0.7...v2.0.8

v2.0.7-ls194

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.7-ls194/index.html

LinuxServer Changes:

Rebase to Alpine 3.22.

Remote Changes:

Major changes in 2.0

• 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:

  • dragonfly/amd64
  • solaris/amd64
  • linux/ppc64
  • netbsd/*
  • openbsd/386 and openbsd/arm
  • windows/arm

• 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.

This release is also available as:

• APT repository: https://apt.syncthing.net/

• Docker image: docker.io/syncthing/syncthing:2.0.7 or ghcr.io/syncthing/syncthing:2.0.7
  ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

• fix(model): earlier free-space check (fixes #10347) by @calmh in syncthing/syncthing#10348
• fix(api): redact device encryption passwords in support bundle config by @pixelspark in syncthing/syncthing#10359
• fix(sqlite): revert to default page cache size by @calmh in syncthing/syncthing#10362
• fix(tlsutil): support HTTP/2 on GUI/API connections by @calmh in syncthing/syncthing#10366
• fix(sqlite): avoid rowid on kv table by @calmh in syncthing/syncthing#10367

Other

• chore(model): adjust folder state logging (fixes #10350) by @calmh in syncthing/syncthing#10353
• build: package for illumos using vmactions/omnios-vm by @trisk in syncthing/syncthing#10328
• chore(slogutil): add configurable logging format (fixes #10352) by @calmh in syncthing/syncthing#10354

New Contributors

• @trisk made their first contribution in syncthing/syncthing#10328

Full Changelog: syncthing/syncthing@v2.0.6...v2.0.7

v2.0.6-ls194

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.6-ls194/index.html

LinuxServer Changes:

Rebase to Alpine 3.22.

Remote Changes:

Major changes in 2.0

• 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:

  • dragonfly/amd64
  • illumos/amd64 and solaris/amd64
  • linux/ppc64
  • netbsd/*
  • openbsd/386 and openbsd/arm
  • windows/arm

• 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.

This release is also available as:

• APT repository: https://apt.syncthing.net/

• Docker image: docker.io/syncthing/syncthing:2.0.6 or ghcr.io/syncthing/syncthing:2.0.6
  ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

• fix(db): remove temp_store = MEMORY pragmas by @calmh in syncthing/syncthing#10343

Full Changelog: syncthing/syncthing@v2.0.5...v2.0.6

v2.0.5-ls194

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.5-ls194/index.html

LinuxServer Changes:

Rebase to Alpine 3.22.

Remote Changes:

Major changes in 2.0

• 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:

  • dragonfly/amd64
  • illumos/amd64 and solaris/amd64
  • linux/ppc64
  • netbsd/*
  • openbsd/386 and openbsd/arm
  • windows/arm

• 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.

This release is also available as:

• APT repository: https://apt.syncthing.net/

• Docker image: docker.io/syncthing/syncthing:2.0.5 or ghcr.io/syncthing/syncthing:2.0.5
  ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

• fix(db): only vacuum database on startup when a migration script was actually run by @pixelspark in syncthing/syncthing#10339

Other

• docs: add DCO requirement to contribution guidelines by @calmh in syncthing/syncthing#10333
• docs: update contribution guidelines from the docs site by @calmh in syncthing/syncthing#10336

Full Changelog: syncthing/syncthing@v2.0.4...v2.0.5

v2.0.4-ls194

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.4-ls194/index.html

LinuxServer Changes:

Rebase to Alpine 3.22.

Remote Changes:

Major changes in 2.0

• 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:

  • dragonfly/amd64
  • illumos/amd64 and solaris/amd64
  • linux/ppc64
  • netbsd/*
  • openbsd/386 and openbsd/arm
  • windows/arm

• 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.

This release is also available as:

• APT repository: https://apt.syncthing.net/

• Docker image: docker.io/syncthing/syncthing:2.0.4 or ghcr.io/syncthing/syncthing:2.0.4
  ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

• fix(cmd): only start temporary API server during migration if it's enabled by @pixelspark in syncthing/syncthing#10284
• fix(model): consider MaxFolderConcurrency when calculating number of hashers by @tomasz1986 in syncthing/syncthing#10285
• fix(model): consider number of CPU cores when calculating hashers on interactive OS (#10284) by @tomasz1986 in syncthing/syncthing#10286
• fix(db): apply all migrations and schema in one transaction by @calmh in syncthing/syncthing#10323
• fix(model): correctly handle block-aligned empty sparse files by @calmh in syncthing/syncthing#10332
• fix(syncthing): apply folder migrations with temporary API/GUI server by @calmh in syncthing/syncthing#10330

Other

• chore(db): adjust db bench name to improve benchstat grouping by @imsodin in syncthing/syncthing#10283
• chore(db): cleanup DB in tests and remove OpenTemp by @imsodin in syncthing/syncthing#10282
• build: use Go 1.24 tools pattern by @calmh in syncthing/syncthing#10281
• chore(db): avoid rowid for blocks and blocklists by @bt90 in syncthing/syncthing#10315
• refactor(db): slightly improve insert performance by @calmh in syncthing/syncthing#10318
• chore(gui): use steps of 1024 KiB for bandwidth rate limits by @tomasz1986 in syncthing/syncthing#10316
• chore(gui): use step of 3600 for versions cleanup interval by @tomasz1986 in syncthing/syncthing#10317
• chore(db): benchmark output, migration blocks/s output by @calmh in syncthing/syncthing#10320
• chore(db): update schema version in the same transaction as migration by @imsodin in syncthing/syncthing#10321
• chore(db): migration for previous commits by @calmh in syncthing/syncthing#10319

Full Changelog: syncthing/syncthing@v2.0.3...v2.0.4

v2.0.3-ls194

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.3-ls194/index.html

LinuxServer Changes:

Rebase to Alpine 3.22.

Remote Changes:

Major changes in 2.0

• 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:

  • dragonfly/amd64
  • illumos/amd64 and solaris/amd64
  • linux/ppc64
  • netbsd/*
  • openbsd/386 and openbsd/arm
  • windows/arm

• 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.

This release is also available as:

• APT repository: https://apt.syncthing.net/

• Docker image: docker.io/syncthing/syncthing:2.0.3 or ghcr.io/syncthing/syncthing:2.0.3
  ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

• fix(cmd): restore --version flag for compatibility by @acolomb in syncthing/syncthing#10269
• fix(cmd): make database migration more robust to write errors by @calmh in syncthing/syncthing#10278
• fix(cmd): provide temporary GUI/API server during database migration by @calmh in syncthing/syncthing#10279
• fix(db): clean files for dropped folders at startup by @calmh in syncthing/syncthing#10280

Other

• chore(slog): re-enable LOGGER_DISCARD (fixes #10262) by @rasa in syncthing/syncthing#10267
• build: downgrade gopsutil (fixes #10276) by @calmh in syncthing/syncthing#10277

Full Changelog: syncthing/syncthing@v2.0.2...v2.0.3

v2.0.3-ls193

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.3-ls193/index.html

LinuxServer Changes:

Rebase to Alpine 3.22.

Remote Changes:

Major changes in 2.0

• 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:

  • dragonfly/amd64
  • illumos/amd64 and solaris/amd64
  • linux/ppc64
  • netbsd/*
  • openbsd/386 and openbsd/arm
  • windows/arm

• 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.

This release is also available as:

• APT repository: https://apt.syncthing.net/

• Docker image: docker.io/syncthing/syncthing:2.0.3 or ghcr.io/syncthing/syncthing:2.0.3
  ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

• fix(cmd): restore --version flag for compatibility by @acolomb in syncthing/syncthing#10269
• fix(cmd): make database migration more robust to write errors by @calmh in syncthing/syncthing#10278
• fix(cmd): provide temporary GUI/API server during database migration by @calmh in syncthing/syncthing#10279
• fix(db): clean files for dropped folders at startup by @calmh in syncthing/syncthing#10280

Other

• chore(slog): re-enable LOGGER_DISCARD (fixes #10262) by @rasa in syncthing/syncthing#10267
• build: downgrade gopsutil (fixes #10276) by @calmh in syncthing/syncthing#10277

Full Changelog: syncthing/syncthing@v2.0.2...v2.0.3

v2.0.2-ls192

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.2-ls192/index.html

LinuxServer Changes:

Rebase to Alpine 3.22.

Remote Changes:

Major changes in 2.0

• 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:

  • dragonfly/amd64
  • illumos/amd64 and solaris/amd64
  • linux/ppc64
  • netbsd/*
  • openbsd/386 and openbsd/arm
  • windows/arm

• 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.

This release is also available as:

• APT repository: https://apt.syncthing.net/

• Docker image: docker.io/syncthing/syncthing:2.0.2 or ghcr.io/syncthing/syncthing:2.0.2
  ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Other

• build: remove netgo and osusergo build tags (fixes #10251) by @calmh in syncthing/syncthing#10256
• build: bump required language level to 1.24, compiler to 1.25 by @calmh in syncthing/syncthing#10248
• build: set netgo & osusergo tags for Linux build by @calmh in syncthing/syncthing#10261

Full Changelog: syncthing/syncthing@v2.0.1...v2.0.2

v2.0.2-ls191

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.2-ls191/index.html

LinuxServer Changes:

Rebase to Alpine 3.22.

Remote Changes:

Major changes in 2.0

• 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:

  • dragonfly/amd64
  • illumos/amd64 and solaris/amd64
  • linux/ppc64
  • netbsd/*
  • openbsd/386 and openbsd/arm
  • windows/arm

• 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.

This release is also available as:

• APT repository: https://apt.syncthing.net/

• Docker image: docker.io/syncthing/syncthing:2.0.2 or ghcr.io/syncthing/syncthing:2.0.2
  ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Other

• build: remove netgo and osusergo build tags (fixes #10251) by @calmh in syncthing/syncthing#10256
• build: bump required language level to 1.24, compiler to 1.25 by @calmh in syncthing/syncthing#10248
• build: set netgo & osusergo tags for Linux build by @calmh in syncthing/syncthing#10261

Full Changelog: syncthing/syncthing@v2.0.1...v2.0.2

v2.0.1-ls190

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.1-ls190/index.html

LinuxServer Changes:

Use double-dash long options for syncthing v2.0.0.

Remote Changes:

Major changes in 2.0

• 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:

  • dragonfly/amd64
  • illumos/amd64 and solaris/amd64
  • linux/ppc64
  • netbsd/*
  • openbsd/386 and openbsd/arm
  • windows/arm

• 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.

This release is also available as:

• APT repository: https://apt.syncthing.net/

• Docker image: docker.io/syncthing/syncthing:2.0.1 or ghcr.io/syncthing/syncthing:2.0.1
  ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

• fix: allow upgrade without config dir (fixes #10240) by @calmh in syncthing/syncthing#10241
• fix(all): various typos by @rasa in syncthing/syncthing#10242
• fix(etc): correct incantation to launch browser in Linux desktop file by @calmh in syncthing/syncthing#10246
• fix(db): handle path names that include URL special chars (fixes #10245) by @calmh in syncthing/syncthing#10247
• fix: increase default delete retention to 15 months by @calmh in syncthing/syncthing#10252

Other

• build(deps): update (most) dependencies by @calmh in syncthing/syncthing#10243

Full Changelog: syncthing/syncthing@v2.0.0...v2.0.1