Update dependency syncthing/syncthing to v2 #1730
Conversation
forking-renovate
bot
added
the
dependencies
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: renovate-bot The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
renovate-bot
force-pushed
the
renovate/major-syncthing
branch
2 times, most recently
from
d87cb65 to
a20419d
Compare
renovate-bot
force-pushed
the
renovate/major-syncthing
branch
from
a20419d to
7b43220
Compare
renovate-bot
force-pushed
the
renovate/major-syncthing
branch
4 times, most recently
from
6d71283 to
35ab125
Compare
renovate-bot
force-pushed
the
renovate/major-syncthing
branch
from
35ab125 to
0a33b0e
Compare
Signed-off-by: Mend Renovate <[email protected]>
renovate-bot
force-pushed
the
renovate/major-syncthing
branch
from
0a33b0e to
fafbe68
Compare
|
|
@renovate-bot: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
This PR contains the following updates:
v1.30.0->v2.0.10Release Notes
syncthing/syncthing (syncthing/syncthing)
v2.0.10Compare 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.10orghcr.io/syncthing/syncthing:2.0.10(
{docker,ghcr}.io/syncthing/syncthing:2to follow just the major version)What's Changed
Fixes
Other
Full Changelog: syncthing/syncthing@v2.0.9...v2.0.10
v2.0.9Compare 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.9orghcr.io/syncthing/syncthing:2.0.9(
{docker,ghcr}.io/syncthing/syncthing:2to follow just the major version)What's Changed
Fixes
Other
Full Changelog: syncthing/syncthing@v2.0.8...v2.0.9
v2.0.8Compare 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.8orghcr.io/syncthing/syncthing:2.0.8(
{docker,ghcr}.io/syncthing/syncthing:2to follow just the major version)What's Changed
Fixes
Other
New Contributors
Full Changelog: syncthing/syncthing@v2.0.7...v2.0.8
v2.0.7Compare 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.7orghcr.io/syncthing/syncthing:2.0.7(
{docker,ghcr}.io/syncthing/syncthing:2to follow just the major version)What's Changed
Fixes
Other
New Contributors
Full Changelog: syncthing/syncthing@v2.0.6...v2.0.7
v2.0.6Compare 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.6orghcr.io/syncthing/syncthing:2.0.6(
{docker,ghcr}.io/syncthing/syncthing:2to follow just the major version)What's Changed
Fixes
Full Changelog: syncthing/syncthing@v2.0.5...v2.0.6
v2.0.5Compare 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.5orghcr.io/syncthing/syncthing:2.0.5(
{docker,ghcr}.io/syncthing/syncthing:2to follow just the major version)What's Changed
Fixes
Other
Full Changelog: syncthing/syncthing@v2.0.4...v2.0.5
v2.0.4Compare 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.4orghcr.io/syncthing/syncthing:2.0.4(
{docker,ghcr}.io/syncthing/syncthing:2to follow just the major version)What's Changed
Fixes
Other
Full Changelog: syncthing/syncthing@v2.0.3...v2.0.4
v2.0.3Compare 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.3orghcr.io/syncthing/syncthing:2.0.3(
{docker,ghcr}.io/syncthing/syncthing:2to follow just the major version)What's Changed
Fixes
Other
Full Changelog: syncthing/syncthing@v2.0.2...v2.0.3
v2.0.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.2orghcr.io/syncthing/syncthing:2.0.2(
{docker,ghcr}.io/syncthing/syncthing:2to follow just the major version)What's Changed
Other
Full Changelog: syncthing/syncthing@v2.0.1...v2.0.2
v2.0.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.1orghcr.io/syncthing/syncthing:2.0.1(
{docker,ghcr}.io/syncthing/syncthing:2to follow just the major version)What's Changed
Fixes
Other
Full Changelog: syncthing/syncthing@v2.0.0...v2.0.1
v2.0.0Compare Source
This is the first release of the new 2.0 series. Expect some rough edges and keep a sense of adventure! 🙏
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 six months. If your use case require deletes to take
effect after more than a six 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.0orghcr.io/syncthing/syncthing:2.0.0(
{docker,ghcr}.io/syncthing/syncthing:2to follow just the major version)What's Changed
Fixes
Features
syncthing debug database-statisticscommand by @calmh in #10117Ed25519keys for sync connections by @calmh in #10162Other
Configuration
📅 Schedule: Branch creation - Between 03:00 AM and 06:59 AM, Monday through Friday ( * 3-6 * * 1-5 ) in timezone America/New_York, 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 was generated by Mend Renovate. View the repository job log.