Update ghcr.io/syncthing/syncthing Docker tag to v2.0.15 #212
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ryuupendragon/docker-compose#212
Reference in New Issue
Block a user
Delete Branch "renovate/ghcr.io-syncthing-syncthing-2.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
2.0.14→2.0.15Release Notes
syncthing/syncthing (ghcr.io/syncthing/syncthing)
v2.0.15Compare 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.15orghcr.io/syncthing/syncthing:2.0.15(
{docker,ghcr}.io/syncthing/syncthing:2to follow just the major version)What's Changed
Fixes
Other
New Contributors
Full Changelog: https://github.com/syncthing/syncthing/compare/v2.0.14...v2.0.15
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.