All Versions
86
Latest Version
Avg Release Cycle
6 days
Latest Release
1374 days ago

Changelog History
Page 4

  • v1.6.0

    June 01, 2020

  • v1.6.0-rc.5 Changes

    May 20, 2020

    v1.6.0

    🚀 This release performs a database schema migration, and adds the
    BlockPullOrder, DisableFsync and MaxConcurrentWrites folder
    🔧 options to the configuration schema.

    The LocalChangeDetected event no longer has the action set to
    added for new files, instead showing modified for all local file
    🔄 changes.

    🛠 Bugfixes:

    • 🔀 #3876: Removing and re-adding a folder may cause data loss
    • 🔀 #5731: 100% CPU every minute on watch setup retry
    • 🔀 #6268: Out of sync panel layout overflows
    • 🔀 #6557: Folder error repeatedly set and unset
    • 🔀 #6559: Deadlock on folder unsubscribe
    • 🔀 #6576: Versioning params in config flip flop in order
    • 🔀 #6578: Allow rescan at folder state "Local Additions"
    • 🔀 #6583: Distributed deadlock on request
    • 🐳 #6604: Docker healthcheck fails when run in host network

    ✨ Enhancements:

    • 🔀 #5224: Accept new connections in place of old ones when appropriate
    • 🔀 #6530: Add "Pause All"/"Resume All" button for devices
    • 🔀 #6541: Limit number of concurrent writes while syncing

    Other issues:

    • 🔀 #6575: Incomprehensible error message: 'directory is not empty; files within are probably ignored on connected devices only'
    • 🔀 #6584: A field in a structure is sometimes protected by Mutex, but sometimes unprotected.

  • v1.6.0-rc.4 Changes

    May 16, 2020

    v1.6.0

    🚀 This release performs a database schema migration, and adds the
    BlockPullOrder, DisableFsync and MaxConcurrentWrites folder
    🔧 options to the configuration schema.

    The LocalChangeDetected event no longer has the action set to
    added for new files, instead showing modified for all local file
    🔄 changes.

    🛠 Bugfixes:

    • 🔀 #3876: Removing and re-adding a folder may cause data loss
    • 🔀 #5731: 100% CPU every minute on watch setup retry
    • 🔀 #6268: Out of sync panel layout overflows
    • 🔀 #6557: Folder error repeatedly set and unset
    • 🔀 #6559: Deadlock on folder unsubscribe
    • 🔀 #6576: Versioning params in config flip flop in order
    • 🔀 #6578: Allow rescan at folder state "Local Additions"
    • 🔀 #6583: Distributed deadlock on request
    • 🐳 #6604: Docker healthcheck fails when run in host network

    ✨ Enhancements:

    • 🔀 #5224: Accept new connections in place of old ones when appropriate
    • 🔀 #6530: Add "Pause All"/"Resume All" button for devices
    • 🔀 #6541: Limit number of concurrent writes while syncing

    Other issues:

    • 🔀 #6575: Incomprehensible error message: 'directory is not empty; files within are probably ignored on connected devices only'
    • 🔀 #6584: A field in a structure is sometimes protected by Mutex, but sometimes unprotected.

  • v1.6.0-rc.3 Changes

    May 16, 2020

    v1.6.0

    🚀 This release performs a database schema migration, and adds the
    BlockPullOrder, DisableFsync and MaxConcurrentWrites folder
    🔧 options to the configuration schema.

    The LocalChangeDetected event no longer has the action set to
    added for new files, instead showing modified for all local file
    🔄 changes.

    🛠 Bugfixes:

    • 🔀 #3876: Removing and re-adding a folder may cause data loss
    • 🔀 #5731: 100% CPU every minute on watch setup retry
    • 🔀 #6268: Out of sync panel layout overflows
    • 🔀 #6557: Folder error repeatedly set and unset
    • 🔀 #6559: Deadlock on folder unsubscribe
    • 🔀 #6576: Versioning params in config flip flop in order
    • 🔀 #6578: Allow rescan at folder state "Local Additions"
    • 🔀 #6583: Distributed deadlock on request
    • 🐳 #6604: Docker healthcheck fails when run in host network

    ✨ Enhancements:

    • 🔀 #5224: Accept new connections in place of old ones when appropriate
    • 🔀 #6530: Add "Pause All"/"Resume All" button for devices
    • 🔀 #6541: Limit number of concurrent writes while syncing

    Other issues:

    • 🔀 #6575: Incomprehensible error message: 'directory is not empty; files within are probably ignored on connected devices only'
    • 🔀 #6584: A field in a structure is sometimes protected by Mutex, but sometimes unprotected.

  • v1.6.0-rc.2 Changes

    May 13, 2020

    🚀 This release performs a database schema migration, and adds the
    BlockPullOrder, DisableFsync and MaxConcurrentWrites folder
    🔧 options to the configuration schema.

    The LocalChangeDetected event no longer has the action set to
    added for new files, instead showing modified for all local file
    🔄 changes.

    🛠 Bugfixes:

    • 🔀 #3876: Removing and re-adding a folder may cause data loss
    • 🔀 #5731: 100% CPU every minute on watch setup retry
    • 🔀 #6268: Out of sync panel layout overflows
    • 🔀 #6557: Folder error repeatedly set and unset
    • 🔀 #6559: Deadlock on folder unsubscribe
    • 🔀 #6576: Versioning params in config flip flop in order
    • 🔀 #6578: Allow rescan at folder state "Local Additions"
    • 🔀 #6583: Distributed deadlock on request
    • 🐳 #6604: Docker healthcheck fails when run in host network

    ✨ Enhancements:

    • 🔀 #5224: Accept new connections in place of old ones when appropriate
    • 🔀 #6530: Add "Pause All"/"Resume All" button for devices
    • 🔀 #6541: Limit number of concurrent writes while syncing

    Other issues:

    • 🔀 #6575: Incomprehensible error message: 'directory is not empty; files within are probably ignored on connected devices only'
    • 🔀 #6584: A field in a structure is sometimes protected by Mutex, but sometimes unprotected.

  • v1.6.0-rc.1

    May 11, 2020

  • v1.5.0

    May 04, 2020

  • v1.5.0-rc.2 Changes

    April 22, 2020

    v1.5.0

    🚀 This release changes the default location for the index database under
    some circumstances. Two new flags can also be used to affect the
    🔧 location of the configuration (-config) and database (-data)
    separately. The old -home flag is equivalent to setting both of these
    to the same directory. When no flags are given the following logic is
    👉 used to determine the data location:

    • 0️⃣ If a database exists in the old default location, that location is
      still used. This means existing installations are not affected by this
      🔄 change.
    • If $XDG_DATA_HOME is set, use $XDG_DATA_HOME/syncthing.
    • 🔀 If ~/.local/share/syncthing exists, use that location.
    • 0️⃣ Use the old default location.

    🏁 This logic is used on non-Windows, non-Mac platforms only. On Windows
    and Mac the logic is unchanged.

    🛠 Bugfixes:

    • 🔀 #3808: gui: Number of days must be number flashes red then disappears
    • 🔀 #5809: stdiscosrv failed to load keypair without proper error message
    • 🔀 #6410: Wrong 30-days-interval in staggered versioning
    • 🔀 #6430: Incorrect out-of-sync/locally changed status indication on folders
    • 🔀 #6436: Revert Local Changes red button does not work correctly
    • 🔀 #6440: Doesn't run monitor process when started with STNORESTART=1
    • 🔀 #6450: LDAP auth doesn't handle LDAPS with certificate validation
    • 🔀 #6487: Scan problem within single unignored subdirectory prevents bidirectional sync

    ✨ Enhancements:

    • #4924: Move index db to $XDG_DATA_HOME/syncthing/
    • 🔀 #5376: Improve LDAP authentication
    • ⬆️ #6384: Do auto upgrades early and synchronously on startup
    • 🔀 #6416: Improve device status for "unused" devices
    • 🔀 #6432: Deleted file that existed locally only reported as locally changed
    • ⬆️ #6437: Don't start browser when restarting after upgrade

    Other issues:

    • 🏁 #6471: Windows exe isn't properly version tagged

  • v1.5.0-rc.1

    April 13, 2020

  • v1.4.2 Changes

    April 08, 2020

    v1.4.2

    ⚡️ This is a tiny update to fix a couple of crashes that should not have
    ⬆️ landed in 1.4.1, and revert a change to the upgrade code that puts
    ⬆️ unnecessary load on the upgrade server.

    🛠 Bugfixes:

    • 🔀 #6499: panic: nil pointer dereference in usage reporting