Skip to content

Releases: linuxserver/docker-syncthing

v2.1.0-ls217

12 May 08:42
0a18bc1

Choose a tag to compare

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.1.0-ls217/index.html

LinuxServer Changes:

Full Changelog: v2.0.16-ls216...v2.1.0-ls217

Remote Changes:

Major changes in 2.1

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

This release is also available as:

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

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

What's Changed

Fixes

Features

Other

New Contributors

Full Changelog: syncthing/syncthing@v2.0.16...v2.1.0

v2.0.16-ls216

09 May 04:20
cfad4ea

Choose a tag to compare

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.16-ls216/index.html

LinuxServer Changes:

Full Changelog: v2.0.16-ls215...v2.0.16-ls216

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.16 or ghcr.io/syncthing/syncthing:2.0.16
    ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

Other

Full Changelog: syncthing/syncthing@v2.0.15...v2.0.16

v2.0.16-ls215

25 Apr 03:50
619f72a

Choose a tag to compare

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.16-ls215/index.html

LinuxServer Changes:

Full Changelog: v2.0.16-ls214...v2.0.16-ls215

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.16 or ghcr.io/syncthing/syncthing:2.0.16
    ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

Other

Full Changelog: syncthing/syncthing@v2.0.15...v2.0.16

v2.0.16-ls214

18 Apr 03:48
19145fd

Choose a tag to compare

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.16-ls214/index.html

LinuxServer Changes:

Full Changelog: v2.0.16-ls213...v2.0.16-ls214

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.16 or ghcr.io/syncthing/syncthing:2.0.16
    ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

Other

Full Changelog: syncthing/syncthing@v2.0.15...v2.0.16

v2.0.16-ls213

07 Apr 16:18
6d3b6e5

Choose a tag to compare

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.16-ls213/index.html

LinuxServer Changes:

Full Changelog: v2.0.15-ls212...v2.0.16-ls213

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.16 or ghcr.io/syncthing/syncthing:2.0.16
    ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

Other

Full Changelog: syncthing/syncthing@v2.0.15...v2.0.16

v2.0.15-ls212

04 Apr 03:33
8f97090

Choose a tag to compare

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.15-ls212/index.html

LinuxServer Changes:

Full Changelog: v2.0.15-ls211...v2.0.15-ls212

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.15 or ghcr.io/syncthing/syncthing:2.0.15
    ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

Other

New Contributors

Full Changelog: syncthing/syncthing@v2.0.14...v2.0.15

v2.0.15-ls211

14 Mar 03:23
2c5c29d

Choose a tag to compare

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.15-ls211/index.html

LinuxServer Changes:

Full Changelog: v2.0.15-ls210...v2.0.15-ls211

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.15 or ghcr.io/syncthing/syncthing:2.0.15
    ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

Other

New Contributors

Full Changelog: syncthing/syncthing@v2.0.14...v2.0.15

v2.0.15-ls210

03 Mar 18:27
872673d

Choose a tag to compare

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.15-ls210/index.html

LinuxServer Changes:

Full Changelog: v2.0.14-ls209...v2.0.15-ls210

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.15 or ghcr.io/syncthing/syncthing:2.0.15
    ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

Other

New Contributors

Full Changelog: syncthing/syncthing@v2.0.14...v2.0.15

v2.0.14-ls209

28 Feb 02:54
d06114a

Choose a tag to compare

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.14-ls209/index.html

LinuxServer Changes:

Full Changelog: v2.0.14-ls208...v2.0.14-ls209

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.14 or ghcr.io/syncthing/syncthing:2.0.14
    ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

Other

New Contributors

Full Changelog: syncthing/syncthing@v2.0.13...v2.0.14

v2.0.14-ls208

14 Feb 03:23
e1ec316

Choose a tag to compare

CI Report:

https://ci-tests.linuxserver.io/linuxserver/syncthing/v2.0.14-ls208/index.html

LinuxServer Changes:

Full Changelog: v2.0.14-ls207...v2.0.14-ls208

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.14 or ghcr.io/syncthing/syncthing:2.0.14
    ({docker,ghcr}.io/syncthing/syncthing:2 to follow just the major version)

What's Changed

Fixes

Other

New Contributors

Full Changelog: syncthing/syncthing@v2.0.13...v2.0.14