fix(deps): update syncthing/syncthing v2.0.15 → v2.0.16#1740
Merged
truecharts-admin merged 1 commit intomainfrom Apr 7, 2026
Merged
fix(deps): update syncthing/syncthing v2.0.15 → v2.0.16#1740truecharts-admin merged 1 commit intomainfrom
truecharts-admin merged 1 commit intomainfrom
Conversation
📦 App Size AnalysisNote Comparing 📈 Size Comparison Table
|
Crow-Control
approved these changes
Apr 7, 2026
Member
Crow-Control
left a comment
Crow-Control
left a comment
There was a problem hiding this comment.
Auto approved automated PR
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.0.15→2.0.16Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
syncthing/syncthing (syncthing/syncthing)
v2.0.16Compare Source
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-levelsets the default log level for allpackages, and the
STTRACEenvironment variable and GUI has been updatedto set log levels per package. The
--verboseand--logflagscommandline 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-intervalcommand line option or correspondingenvironment 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.
-homemust be given as--home. Some optionshave been renamed, others have become subcommands. All serve options are
now also accepted as environment variables. See
syncthing --helpandsyncthing serve --helpfor details.Rolling hash detection of shifted data is no longer supported as this
effectively never helped. Instead, scanning and syncing is faster and more
efficient without it.
A "default folder" is no longer created on first startup.
Multiple connections are now used by default between v2 devices. The new
default value is to use three connections: one for index metadata and two
for data exchange.
The following platforms unfortunately no longer get prebuilt binaries for
download at syncthing.net and on GitHub, due to complexities related to
cross compilation with SQLite:
The handling of conflict resolution involving deleted files has changed. A
delete can now be the winning outcome of conflict resolution, resulting in
the deleted file being moved to a conflict copy.
This release is also available as:
APT repository: https://apt.syncthing.net/
Docker image:
docker.io/syncthing/syncthing:2.0.16orghcr.io/syncthing/syncthing:2.0.16(
{docker,ghcr}.io/syncthing/syncthing:2to follow just the major version)What's Changed
Fixes
Other
Full Changelog: syncthing/syncthing@v2.0.15...v2.0.16
v2.0.16-rc.2Compare Source
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-levelsets the default log level for allpackages, and the
STTRACEenvironment variable and GUI has been updatedto set log levels per package. The
--verboseand--logflagscommandline 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-intervalcommand line option or correspondingenvironment 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.
-homemust be given as--home. Some optionshave been renamed, others have become subcommands. All serve options are
now also accepted as environment variables. See
syncthing --helpandsyncthing serve --helpfor details.Rolling hash detection of shifted data is no longer supported as this
effectively never helped. Instead, scanning and syncing is faster and more
efficient without it.
A "default folder" is no longer created on first startup.
Multiple connections are now used by default between v2 devices. The new
default value is to use three connections: one for index metadata and two
for data exchange.
The following platforms unfortunately no longer get prebuilt binaries for
download at syncthing.net and on GitHub, due to complexities related to
cross compilation with SQLite:
The handling of conflict resolution involving deleted files has changed. A
delete can now be the winning outcome of conflict resolution, resulting in
the deleted file being moved to a conflict copy.
This release is also available as:
APT repository: https://apt.syncthing.net/
Docker image:
docker.io/syncthing/syncthing:2.0.16-rc.2orghcr.io/syncthing/syncthing:2.0.16-rc.2(
{docker,ghcr}.io/syncthing/syncthing:2to follow just the major version)What's Changed
Fixes
Other
Full Changelog: syncthing/syncthing@v2.0.15...v2.0.16-rc.2
v2.0.16-rc.1Compare Source
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-levelsets the default log level for allpackages, and the
STTRACEenvironment variable and GUI has been updatedto set log levels per package. The
--verboseand--logflagscommandline 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-intervalcommand line option or correspondingenvironment 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.
-homemust be given as--home. Some optionshave been renamed, others have become subcommands. All serve options are
now also accepted as environment variables. See
syncthing --helpandsyncthing serve --helpfor details.Rolling hash detection of shifted data is no longer supported as this
effectively never helped. Instead, scanning and syncing is faster and more
efficient without it.
A "default folder" is no longer created on first startup.
Multiple connections are now used by default between v2 devices. The new
default value is to use three connections: one for index metadata and two
for data exchange.
The following platforms unfortunately no longer get prebuilt binaries for
download at syncthing.net and on GitHub, due to complexities related to
cross compilation with SQLite:
The handling of conflict resolution involving deleted files has changed. A
delete can now be the winning outcome of conflict resolution, resulting in
the deleted file being moved to a conflict copy.
This release is also available as:
APT repository: https://apt.syncthing.net/
Docker image:
docker.io/syncthing/syncthing:2.0.16-rc.1orghcr.io/syncthing/syncthing:2.0.16-rc.1(
{docker,ghcr}.io/syncthing/syncthing:2to follow just the major version)What's Changed
Other
Full Changelog: syncthing/syncthing@v2.0.15...v2.0.16-rc.1
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.