登录
注册
开源
企业版
高校版
搜索
帮助中心
使用条款
关于我们
开源
企业版
高校版
私有云
模力方舟
AI 队友
登录
注册
3月21日 深圳｜OpenClaw 线下实战沙龙：招聘、资讯、项目协同三大场景实操，VS ZeroClaw 横向对比评测，别再只会装，来现场跑通真实业务！
代码拉取完成，页面将自动刷新
开源项目
>
程序开发
>
网络工具
&&
捐赠
捐赠前请先登录
取消
前往登录
扫描微信二维码支付
取消
支付完成
支付提示
将跳转至支付宝完成支付
确定
取消
Watch
不关注
关注所有动态
仅关注版本发行动态
关注但不提醒动态
22
Star
155
Fork
46
Gitee 极速下载
/
syncthing
代码
Wiki
统计
流水线
服务
质量分析
Jenkins for Gitee
腾讯云托管
腾讯云 Serverless
悬镜安全
阿里云 SAE
Codeblitz
SBOM
我知道了，不再自动展开
标签
标签名
描述
提交信息
操作
v2.0.16-rc.2
## 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-rc.2` or `ghcr.io/syncthing/syncthing:2.0.16-rc.2` (`{docker,ghcr}.io/syncthing/syncthing:2` to follow just the major version) ## What's Changed ### Fixes * fix(protocol): verify compressed message length before decompression by @calmh in https://github.com/syncthing/syncthing/pull/10595 * fix(systemd): support overrides for syncOwnership by @Valloric in https://github.com/syncthing/syncthing/pull/10602 * fix(systemd): add back chown allowed syscalls by @Valloric in https://github.com/syncthing/syncthing/pull/10605 ### Other * chore(config, connections): use same reconnection interval for QUIC and TCP (fixes #10507) by @marbens-arch in https://github.com/syncthing/syncthing/pull/10573 * build(deps): update dependencies by @calmh in https://github.com/syncthing/syncthing/pull/10588 * chore(sqlite): reduce max open connections, keep them open permanently (fixes #10592) by @calmh in https://github.com/syncthing/syncthing/pull/10596 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.15...v2.0.16-rc.2
9ffce6e
2026-03-13 20:03
下载
v2.0.16-rc.1
## 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-rc.1` or `ghcr.io/syncthing/syncthing:2.0.16-rc.1` (`{docker,ghcr}.io/syncthing/syncthing:2` to follow just the major version) ## What's Changed ### Other * chore(config, connections): use same reconnection interval for QUIC and TCP (fixes #10507) by @marbens-arch in https://github.com/syncthing/syncthing/pull/10573 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.15...v2.0.16-rc.1
9c7e34b
2026-03-04 05:36
下载
v2.0.15
## 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 * fix(gui): show restarting modal during upgrade restart (fixes #1248) by @steadytao in https://github.com/syncthing/syncthing/pull/10566 * fix(gui): remove width limit for language select items by @EastSun5566 in https://github.com/syncthing/syncthing/pull/10531 ### Other * chore(gui): add id and name to Stay logged in checkbox for password managers by @epifeny in https://github.com/syncthing/syncthing/pull/10558 * chore(db): add ability to wait for programmatically started database maintenance, query last maintenance time by @pixelspark in https://github.com/syncthing/syncthing/pull/10565 * chore(etc): add comprehensive sandboxing by @Valloric in https://github.com/syncthing/syncthing/pull/10421 * chore: build with Go 1.26; use Go 1.25 features by @calmh in https://github.com/syncthing/syncthing/pull/10570 ## New Contributors * @epifeny made their first contribution in https://github.com/syncthing/syncthing/pull/10558 * @steadytao made their first contribution in https://github.com/syncthing/syncthing/pull/10566 * @EastSun5566 made their first contribution in https://github.com/syncthing/syncthing/pull/10531 * @Valloric made their first contribution in https://github.com/syncthing/syncthing/pull/10421 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.14...v2.0.15
dc2a77a
2026-02-11 18:41
下载
v2.0.15-rc.1
## 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-rc.1` or `ghcr.io/syncthing/syncthing:2.0.15-rc.1` (`{docker,ghcr}.io/syncthing/syncthing:2` to follow just the major version) ## What's Changed ### Fixes * fix(gui): show restarting modal during upgrade restart (fixes #1248) by @steadytao in https://github.com/syncthing/syncthing/pull/10566 * fix(gui): remove width limit for language select items by @EastSun5566 in https://github.com/syncthing/syncthing/pull/10531 ### Other * chore(gui): add id and name to Stay logged in checkbox for password managers by @epifeny in https://github.com/syncthing/syncthing/pull/10558 * chore(db): add ability to wait for programmatically started database maintenance, query last maintenance time by @pixelspark in https://github.com/syncthing/syncthing/pull/10565 * chore(etc): add comprehensive sandboxing by @Valloric in https://github.com/syncthing/syncthing/pull/10421 * chore: build with Go 1.26; use Go 1.25 features by @calmh in https://github.com/syncthing/syncthing/pull/10570 ## New Contributors * @epifeny made their first contribution in https://github.com/syncthing/syncthing/pull/10558 * @steadytao made their first contribution in https://github.com/syncthing/syncthing/pull/10566 * @EastSun5566 made their first contribution in https://github.com/syncthing/syncthing/pull/10531 * @Valloric made their first contribution in https://github.com/syncthing/syncthing/pull/10421 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.14...v2.0.15-rc.1
dc2a77a
2026-02-11 18:41
下载
v2.0.14
## 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 * fix(beacon): skip point-to-point interfaces on Android by @bt90 in https://github.com/syncthing/syncthing/pull/10504 * fix(stdiscosrv): use fmt.Println for version output (fixes #10523) by @maishivamhoo123 in https://github.com/syncthing/syncthing/pull/10527 * fix(stdiscosrv): log full device ID on startup by @maishivamhoo123 in https://github.com/syncthing/syncthing/pull/10541 ### Other * chore(api): remove charset declaration from JSON content-type (fixes #10500) by @prathik8794 in https://github.com/syncthing/syncthing/pull/10508 * chore(sqlite): allow periodic database maintenance to be disabled by @pixelspark in https://github.com/syncthing/syncthing/pull/10441 * chore(gui): include license files for fork-awesome assets by @gotmax23 in https://github.com/syncthing/syncthing/pull/10539 * build: add build attestation step at release by @calmh in https://github.com/syncthing/syncthing/pull/10540 ## New Contributors * @prathik8794 made their first contribution in https://github.com/syncthing/syncthing/pull/10508 * @gotmax23 made their first contribution in https://github.com/syncthing/syncthing/pull/10539 * @maishivamhoo123 made their first contribution in https://github.com/syncthing/syncthing/pull/10527 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.13...v2.0.14
b40f2ac
2026-02-02 12:32
下载
v2.0.14-rc.2
## 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-rc.2` or `ghcr.io/syncthing/syncthing:2.0.14-rc.2` (`{docker,ghcr}.io/syncthing/syncthing:2` to follow just the major version) ## What's Changed ### Fixes * fix(beacon): skip point-to-point interfaces on Android by @bt90 in https://github.com/syncthing/syncthing/pull/10504 * fix(stdiscosrv): use fmt.Println for version output (fixes #10523) by @maishivamhoo123 in https://github.com/syncthing/syncthing/pull/10527 * fix(stdiscosrv): log full device ID on startup by @maishivamhoo123 in https://github.com/syncthing/syncthing/pull/10541 ### Other * chore(api): remove charset declaration from JSON content-type (fixes #10500) by @prathik8794 in https://github.com/syncthing/syncthing/pull/10508 * chore(sqlite): allow periodic database maintenance to be disabled by @pixelspark in https://github.com/syncthing/syncthing/pull/10441 * chore(gui): include license files for fork-awesome assets by @gotmax23 in https://github.com/syncthing/syncthing/pull/10539 * build: add build attestation step at release by @calmh in https://github.com/syncthing/syncthing/pull/10540 ## New Contributors * @prathik8794 made their first contribution in https://github.com/syncthing/syncthing/pull/10508 * @gotmax23 made their first contribution in https://github.com/syncthing/syncthing/pull/10539 * @maishivamhoo123 made their first contribution in https://github.com/syncthing/syncthing/pull/10527 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.13...v2.0.14-rc.2
c9f0c1c
2026-01-26 12:12
下载
v2.0.14-rc.1
## 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-rc.1` or `ghcr.io/syncthing/syncthing:2.0.14-rc.1` (`{docker,ghcr}.io/syncthing/syncthing:2` to follow just the major version) ## What's Changed ### Fixes * fix(beacon): skip point-to-point interfaces on Android by @bt90 in https://github.com/syncthing/syncthing/pull/10504 * fix(stdiscosrv): use fmt.Println for version output (fixes #10523) by @maishivamhoo123 in https://github.com/syncthing/syncthing/pull/10527 ### Other * chore(api): remove charset declaration from JSON content-type (fixes #10500) by @prathik8794 in https://github.com/syncthing/syncthing/pull/10508 * chore(sqlite): allow periodic database maintenance to be disabled by @pixelspark in https://github.com/syncthing/syncthing/pull/10441 * chore(gui): include license files for fork-awesome assets by @gotmax23 in https://github.com/syncthing/syncthing/pull/10539 * build: add build attestation step at release by @calmh in https://github.com/syncthing/syncthing/pull/10540 ## New Contributors * @prathik8794 made their first contribution in https://github.com/syncthing/syncthing/pull/10508 * @gotmax23 made their first contribution in https://github.com/syncthing/syncthing/pull/10539 * @maishivamhoo123 made their first contribution in https://github.com/syncthing/syncthing/pull/10527 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.13...v2.0.14-rc.1
a5de148
2026-01-24 19:06
下载
v2.0.13
## 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.13` or `ghcr.io/syncthing/syncthing:2.0.13` (`{docker,ghcr}.io/syncthing/syncthing:2` to follow just the major version) ## What's Changed ### Fixes * fix(beacon): don't join multicast groups on non-multicast interfaces (fixes #10497) by @marbens-arch in https://github.com/syncthing/syncthing/pull/10498 ### Other * chore(model): refactor context handling for folder type by @calmh in https://github.com/syncthing/syncthing/pull/10472 * build: fix docker build by ensuring qemu by @calmh in https://github.com/syncthing/syncthing/pull/10492 * chore(beacon): more verbose debug logging by @marbens-arch in https://github.com/syncthing/syncthing/pull/10496 * build: fix hash failure by limiting globbing by @calmh in https://github.com/syncthing/syncthing/pull/10505 * chore: tweak pull retry logic by @calmh in https://github.com/syncthing/syncthing/pull/10491 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.12...v2.0.13
962b917
2025-12-23 16:10
下载
v2.0.13-rc.1
## 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.13-rc.1` or `ghcr.io/syncthing/syncthing:2.0.13-rc.1` (`{docker,ghcr}.io/syncthing/syncthing:2` to follow just the major version) ## What's Changed ### Fixes * fix(beacon): don't join multicast groups on non-multicast interfaces (fixes #10497) by @marbens-arch in https://github.com/syncthing/syncthing/pull/10498 ### Other * chore(model): refactor context handling for folder type by @calmh in https://github.com/syncthing/syncthing/pull/10472 * build: fix docker build by ensuring qemu by @calmh in https://github.com/syncthing/syncthing/pull/10492 * chore(beacon): more verbose debug logging by @marbens-arch in https://github.com/syncthing/syncthing/pull/10496 * build: fix hash failure by limiting globbing by @calmh in https://github.com/syncthing/syncthing/pull/10505 * chore: tweak pull retry logic by @calmh in https://github.com/syncthing/syncthing/pull/10491 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.12...v2.0.13-rc.1
962b917
2025-12-23 16:10
下载
v2.0.12
## 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.12` or `ghcr.io/syncthing/syncthing:2.0.12` (`{docker,ghcr}.io/syncthing/syncthing:2` to follow just the major version) ## What's Changed ### Other * chore: update quic-go, adapt to lack of write tracking by @calmh in https://github.com/syncthing/syncthing/pull/10456 * chore(cli): clean up generated usage strings for config commands (fixes #10462) by @acolomb in https://github.com/syncthing/syncthing/pull/10463 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.11...v2.0.12
ce884e5
2025-11-24 23:49
下载
v2.0.12-rc.1
## 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.12-rc.1` or `ghcr.io/syncthing/syncthing:2.0.12-rc.1` (`{docker,ghcr}.io/syncthing/syncthing:2` to follow just the major version) ## What's Changed ### Other * chore: update quic-go, adapt to lack of write tracking by @calmh in https://github.com/syncthing/syncthing/pull/10456 * chore(cli): clean up generated usage strings for config commands (fixes #10462) by @acolomb in https://github.com/syncthing/syncthing/pull/10463 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.11...v2.0.12-rc.1
ce884e5
2025-11-24 23:49
下载
v2.0.11
## 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.11` or `ghcr.io/syncthing/syncthing:2.0.11` (`{docker,ghcr}.io/syncthing/syncthing:2` to follow just the major version) ## What's Changed ### Fixes * fix(policy): only allow approvals by non-author contributors by @marbens-arch in https://github.com/syncthing/syncthing/pull/10419 * fix(fs): store `getExpireAdd` mutex in `caseCache` (fixes #9836) by @marbens-arch in https://github.com/syncthing/syncthing/pull/10430 * fix(fs): apply case option to fakefs in casefs tests by @marbens-arch in https://github.com/syncthing/syncthing/pull/10439 * fix(fs): only apply case option to fakefs in stress test by @marbens-arch in https://github.com/syncthing/syncthing/pull/10440 ### Other * docs(docker): make host network mode the default by @bt90 in https://github.com/syncthing/syncthing/pull/10416 * chore(upnp): remove incorrect embedding of nat.Service (fixes #10426) by @imsodin in https://github.com/syncthing/syncthing/pull/10428 * chore: minor lint fixes by @calmh in https://github.com/syncthing/syncthing/pull/10436 * chore(gui): add Azerbaijani (az) and Kurdish (ckb) l10n templates. by @acolomb in https://github.com/syncthing/syncthing/pull/10442 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.10...v2.0.11
81c99e0
2025-10-27 11:59
下载
v2.0.11-rc.1
## 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.11-rc.1` or `ghcr.io/syncthing/syncthing:2.0.11-rc.1` (`{docker,ghcr}.io/syncthing/syncthing:2` to follow just the major version) ## What's Changed ### Fixes * fix(policy): only allow approvals by non-author contributors by @marbens-arch in https://github.com/syncthing/syncthing/pull/10419 * fix(fs): store `getExpireAdd` mutex in `caseCache` (fixes #9836) by @marbens-arch in https://github.com/syncthing/syncthing/pull/10430 * fix(fs): apply case option to fakefs in casefs tests by @marbens-arch in https://github.com/syncthing/syncthing/pull/10439 * fix(fs): only apply case option to fakefs in stress test by @marbens-arch in https://github.com/syncthing/syncthing/pull/10440 ### Other * docs(docker): make host network mode the default by @bt90 in https://github.com/syncthing/syncthing/pull/10416 * chore(upnp): remove incorrect embedding of nat.Service (fixes #10426) by @imsodin in https://github.com/syncthing/syncthing/pull/10428 * chore: minor lint fixes by @calmh in https://github.com/syncthing/syncthing/pull/10436 * chore(gui): add Azerbaijani (az) and Kurdish (ckb) l10n templates. by @acolomb in https://github.com/syncthing/syncthing/pull/10442 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.10...v2.0.11-rc.1
81c99e0
2025-10-27 11:59
下载
v2.0.10
## 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.10` or `ghcr.io/syncthing/syncthing:2.0.10` (`{docker,ghcr}.io/syncthing/syncthing:2` to follow just the major version) ## What's Changed ### Fixes * fix: improve conflict detection by tracking previous file hash (fixes #10349) by @calmh in https://github.com/syncthing/syncthing/pull/10351 * fix(ur): properly skip zero/empty fields in report by @calmh in https://github.com/syncthing/syncthing/pull/10394 * fix(gui): don't fetch usage report preview unnecessarily on GUI load by @calmh in https://github.com/syncthing/syncthing/pull/10395 * fix(db): only perform foreign key checking when a migration was applied by @pixelspark in https://github.com/syncthing/syncthing/pull/10397 * fix(syncthing): do not perform CPU benchmark on startup unless logging enabled by @pixelspark in https://github.com/syncthing/syncthing/pull/10398 * fix(model): don't announce untrusted devices to other devices (fixes #10393) by @calmh in https://github.com/syncthing/syncthing/pull/10408 * fix(sqlite): actually always insert blocks for local files (fixes #10388) by @calmh in https://github.com/syncthing/syncthing/pull/10411 ### Other * build: update GitHub actions by @mrclmr in https://github.com/syncthing/syncthing/pull/10399 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.9...v2.0.10
6f0acac
2025-09-23 20:46
下载
v2.0.10-rc.1
## 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.10-rc.1` or `ghcr.io/syncthing/syncthing:2.0.10-rc.1` (`{docker,ghcr}.io/syncthing/syncthing:2` to follow just the major version) ## What's Changed ### Fixes * fix: improve conflict detection by tracking previous file hash (fixes #10349) by @calmh in https://github.com/syncthing/syncthing/pull/10351 * fix(ur): properly skip zero/empty fields in report by @calmh in https://github.com/syncthing/syncthing/pull/10394 * fix(gui): don't fetch usage report preview unnecessarily on GUI load by @calmh in https://github.com/syncthing/syncthing/pull/10395 * fix(db): only perform foreign key checking when a migration was applied by @pixelspark in https://github.com/syncthing/syncthing/pull/10397 * fix(syncthing): do not perform CPU benchmark on startup unless logging enabled by @pixelspark in https://github.com/syncthing/syncthing/pull/10398 * fix(model): don't announce untrusted devices to other devices (fixes #10393) by @calmh in https://github.com/syncthing/syncthing/pull/10408 * fix(sqlite): actually always insert blocks for local files (fixes #10388) by @calmh in https://github.com/syncthing/syncthing/pull/10411 ### Other * build: update GitHub actions by @mrclmr in https://github.com/syncthing/syncthing/pull/10399 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.9...v2.0.10-rc.1
6f0acac
2025-09-23 20:46
下载
v2.0.9
## 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.9` or `ghcr.io/syncthing/syncthing:2.0.9` (`{docker,ghcr}.io/syncthing/syncthing:2` to follow just the major version) ## What's Changed ### Fixes * fix(sqlite): add _txlock=immediate to modernc implementation by @calmh in https://github.com/syncthing/syncthing/pull/10384 * fix(api): limit size of allowed authentication request by @calmh in https://github.com/syncthing/syncthing/pull/10386 ### Other * chore(ursrv): update regex patterns for Syncthing-Fork entries by @Catfriend1 in https://github.com/syncthing/syncthing/pull/10380 * chore: clean up migrated database by @calmh in https://github.com/syncthing/syncthing/pull/10381 * chore(sqlite): use normalised tables for file names and versions by @calmh in https://github.com/syncthing/syncthing/pull/10383 * chore(model): slightly deflake TestRecvOnlyRevertOwnID by @calmh in https://github.com/syncthing/syncthing/pull/10390 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.8...v2.0.9
3382ccc
2025-09-12 17:41
下载
v2.0.8
## 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 https://github.com/syncthing/syncthing/pull/10374 * fix(sqlite): explicitly set temporary directory location (fixes #10368) by @calmh in https://github.com/syncthing/syncthing/pull/10376 ### Other * build: trigger nightly build only on syncthing repo by @aminvakil in https://github.com/syncthing/syncthing/pull/10375 * chore(scanner): always return values to the pools when hashing blocks by @imsodin in https://github.com/syncthing/syncthing/pull/10377 * chore(sqlite): skip database GC entirely when it's provably unnecessary by @calmh in https://github.com/syncthing/syncthing/pull/10379 ## New Contributors * @aminvakil made their first contribution in https://github.com/syncthing/syncthing/pull/10375 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.7...v2.0.8
25ae01b
2025-09-08 14:55
下载
v2.0.7
## 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 https://github.com/syncthing/syncthing/pull/10348 * fix(api): redact device encryption passwords in support bundle config by @pixelspark in https://github.com/syncthing/syncthing/pull/10359 * fix(sqlite): revert to default page cache size by @calmh in https://github.com/syncthing/syncthing/pull/10362 * fix(tlsutil): support HTTP/2 on GUI/API connections by @calmh in https://github.com/syncthing/syncthing/pull/10366 * fix(sqlite): avoid rowid on kv table by @calmh in https://github.com/syncthing/syncthing/pull/10367 ### Other * chore(model): adjust folder state logging (fixes #10350) by @calmh in https://github.com/syncthing/syncthing/pull/10353 * build: package for illumos using vmactions/omnios-vm by @trisk in https://github.com/syncthing/syncthing/pull/10328 * chore(slogutil): add configurable logging format (fixes #10352) by @calmh in https://github.com/syncthing/syncthing/pull/10354 ## New Contributors * @trisk made their first contribution in https://github.com/syncthing/syncthing/pull/10328 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.6...v2.0.7
3c9e87d
2025-09-05 17:51
下载
v2.0.6
## 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 https://github.com/syncthing/syncthing/pull/10343 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.5...v2.0.6
372e3c2
2025-09-03 15:27
下载
v2.0.5
## 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 https://github.com/syncthing/syncthing/pull/10339 ### Other * docs: add DCO requirement to contribution guidelines by @calmh in https://github.com/syncthing/syncthing/pull/10333 * docs: update contribution guidelines from the docs site by @calmh in https://github.com/syncthing/syncthing/pull/10336 **Full Changelog**: https://github.com/syncthing/syncthing/compare/v2.0.4...v2.0.5
6e9ccf7
2025-09-03 03:03
下载
下载
请输入验证码，防止盗链导致资源被占用
取消
下载
Go
1
https://gitee.com/mirrors/syncthing.git
git@gitee.com:mirrors/syncthing.git
mirrors
syncthing
syncthing
点此查找更多帮助
搜索帮助
Git 命令在线学习
如何在 Gitee 导入 GitHub 仓库
Git 仓库基础操作
企业版和社区版功能对比
SSH 公钥设置
如何处理代码冲突
仓库体积过大，如何减小？
如何找回被删除的仓库数据
Gitee 产品配额说明
GitHub仓库快速导入Gitee及同步更新
什么是 Release（发行版）
将 PHP 项目自动发布到 packagist.org
评论
仓库举报
回到顶部
登录提示
该操作需登录 Gitee 帐号，请先登录后再操作。
立即登录
没有帐号，去注册
