Changelog History
Page 3
-
v1.9.0-rc.1 Changes
August 18, 2020v1.9.0
π This release adds the advanced folder option
caseSensitiveFS
π (https://docs.syncthing.net/advanced/folder-caseSensitiveFS.html) to
disable the new safe handling of case insensitive filesystems.π Bugfixes:
- π #1787: Case-only renames break stuff
- π #5708: Properly handle upper-/lowercase-only file name collisions
- π #6613: TestWatchRename test fails on FreeBSD.
- π #6793: Error status should take precedence over Local Additions
- π #6850: Global state incorrect when ignoring local change
- π #6864: Folder incorrectly marked βUp to Dateβ after switching from βReceive Onlyβ to βSend & Receiveβ
- π #6867: Certificate error when built with Go 1.15
- π #6886: chmod permission after editing .stignore via WebUI not preserved
- π #6892: Syncthing 1.8.0 trying to connect via wrong network route
β¨ Enhancements:
-
v1.8.0 Changes
August 11, 2020v1.8.0
π This release:
β adds the experimental
copyRangeMethod
config on folders, for use on
π filesystems with copy-on-write support. Please see
π https://docs.syncthing.net/advanced/folder-copyrangemethod.html for
details.β adds TCP hole punching, used to establish high performance TCP
connections in certain NAT scenarios where only relay or QUIC
connections could be used previously.β adds a configuration to file versioning for how often to run cleanup.
π§ This defaults to once an hour, but is configurable from very
frequently to never.π Bugfixes:
- π #5425: Allow editing ignore patterns texterea in GUI's folder dialog even when #include fails
- π #6733: strelaysrv can't propely unmarshall a response when joining a pool
- π #6784: Remote device completion 100% while it is actually syncing
- π #6816: fatal error: concurrent map read and map write
- π #6823: Syncthing 1.7.0 performs UPnP with NAT traversal disabled
- π #6825: "pull: no such file" for existing untouched files
β¨ Enhancements:
- π #4259: Attempt TCP hole punching
- π #4271: Make use of filesystems that can handle copies efficiently.
- π #6075: Feature: API check sync status of folder[s]
- π #6313: Improving disk access control in folders with file versioning
- π #6565: Create versioning directory recursively (creating parents as necessary)
- π #6795: Don't warn encountering an invalid path separator for deleted items
- π #6807: "File Pull Order" should be disabled (greyed out) for "Send Only" folders in the GUI
- π³ #6832: Support running syncthing Docker image as non-root user
-
v1.8.0-rc.4 Changes
August 07, 2020v1.8.0
π This release:
β adds the experimental
copyRangeMethod
config on folders, for use on
π filesystems with copy-on-write support. Please see
π https://docs.syncthing.net/advanced/folder-copyrangemethod.html for
details.β adds TCP hole punching, used to establish high performance TCP
connections in certain NAT scenarios where only relay or QUIC
connections could be used previously.β adds a configuration to file versioning for how often to run cleanup.
π§ This defaults to once an hour, but is configurable from very
frequently to never.π Bugfixes:
- π #5425: Allow editing ignore patterns texterea in GUI's folder dialog even when #include fails
- π #6733: strelaysrv can't propely unmarshall a response when joining a pool
- π #6784: Remote device completion 100% while it is actually syncing
- π #6816: fatal error: concurrent map read and map write
- π #6823: Syncthing 1.7.0 performs UPnP with NAT traversal disabled
β¨ Enhancements:
- π #4259: Attempt TCP hole punching
- π #4271: Make use of filesystems that can handle copies efficiently.
- π #6075: Feature: API check sync status of folder[s]
- π #6313: Improving disk access control in folders with file versioning
- π #6565: Create versioning directory recursively (creating parents as necessary)
- π #6795: Don't warn encountering an invalid path separator for deleted items
- π #6807: "File Pull Order" should be disabled (greyed out) for "Send Only" folders in the GUI
- π³ #6832: Support running syncthing Docker image as non-root user
-
v1.8.0-rc.3 Changes
July 28, 2020v1.8.0
π This release:
β adds the experimental
copyRangeMethod
config on folders, for use on
π filesystems with copy-on-write support. Please see
π https://docs.syncthing.net/advanced/folder-copyrangemethod.html for
details.β adds TCP hole punching, used to establish high performance TCP
connections in certain NAT scenarios where only relay or QUIC
connections could be used previously.β adds a configuration to file versioning for how often to run cleanup.
π§ This defaults to once an hour, but is configurable from very
frequently to never.π Bugfixes:
- π #5425: Allow editing ignore patterns texterea in GUI's folder dialog even when #include fails
- π #6733: strelaysrv can't propely unmarshall a response when joining a pool
- π #6784: Remote device completion 100% while it is actually syncing
- π #6816: fatal error: concurrent map read and map write
- π #6823: Syncthing 1.7.0 performs UPnP with NAT traversal disabled
β¨ Enhancements:
- π #4259: Attempt TCP hole punching
- π #4271: Make use of filesystems that can handle copies efficiently.
- π #6075: Feature: API check sync status of folder[s]
- π #6313: Improving disk access control in folders with file versioning
- π #6565: Create versioning directory recursively (creating parents as necessary)
- π #6795: Don't warn encountering an invalid path separator for deleted items
- π #6807: "File Pull Order" should be disabled (greyed out) for "Send Only" folders in the GUI
- π³ #6832: Support running syncthing Docker image as non-root user
-
v1.8.0-rc.2 Changes
July 16, 2020v1.8.0
π This release:
β adds the experimental
copyRangeMethod
config on folders, for use on
π filesystems with copy-on-write support. Please see
π https://docs.syncthing.net/advanced/folder-copyrangemethod.html for
details.β adds TCP hole punching, used to establish high performance TCP
connections in certain NAT scenarios where only relay or QUIC
connections could be used previously.β adds a configuration to file versioning for how often to run cleanup.
π§ This defaults to once an hour, but is configurable from very
frequently to never.π Bugfixes:
- π #5425: Allow editing ignore patterns texterea in GUI's folder dialog even when #include fails
- π #6733: strelaysrv can't propely unmarshall a response when joining a pool
- π #6784: Remote device completion 100% while it is actually syncing
- π #6816: fatal error: concurrent map read and map write
- π #6823: Syncthing 1.7.0 performs UPnP with NAT traversal disabled
β¨ Enhancements:
- π #4259: Attempt TCP hole punching
- π #4271: Make use of filesystems that can handle copies efficiently.
- π #6075: Feature: API check sync status of folder[s]
- π #6313: Improving disk access control in folders with file versioning
- π #6565: Create versioning directory recursively (creating parents as necessary)
- π #6795: Don't warn encountering an invalid path separator for deleted items
- π #6807: "File Pull Order" should be disabled (greyed out) for "Send Only" folders in the GUI
- π³ #6832: Support running syncthing Docker image as non-root user
-
v1.8.0-rc.1 Changes
July 15, 2020v1.8.0
π This release:
β adds the experimental
copyRangeMethod
config on folders, for use on
π filesystems with copy-on-write support. Please see
π https://docs.syncthing.net/advanced/folder-copyrangemethod.html for
details.β adds TCP hole punching, used to establish high performance TCP
connections in certain NAT scenarios where only relay or QUIC
connections could be used previously.β adds a configuration to file versioning for how often to run cleanup.
π§ This defaults to once an hour, but is configurable from very
frequently to never.π Bugfixes:
- π #5425: Allow editing ignore patterns texterea in GUI's folder dialog even when #include fails
- π #6733: strelaysrv can't propely unmarshall a response when joining a pool
- π #6784: Remote device completion 100% while it is actually syncing
- π #6816: fatal error: concurrent map read and map write
- π #6823: Syncthing 1.7.0 performs UPnP with NAT traversal disabled
β¨ Enhancements:
- π #4259: Attempt TCP hole punching
- π #4271: Make use of filesystems that can handle copies efficiently.
- π #6075: Feature: API check sync status of folder[s]
- π #6313: Improving disk access control in folders with file versioning
- π #6565: Create versioning directory recursively (creating parents as necessary)
- π #6795: Don't warn encountering an invalid path separator for deleted items
- π #6807: "File Pull Order" should be disabled (greyed out) for "Send Only" folders in the GUI
- π³ #6832: Support running syncthing Docker image as non-root user
-
v1.7.1 Changes
July 14, 2020π This hotfix release fixes an issue with block validation.
π Bugfixes:
- π #6827: syncthing 1.6.1 -> 1.7.0 fails on "failed validating data"
-
v1.7.0 Changes
July 07, 2020v1.7.0
π This release performs a database migration to optimize for clusters with
many devices.π Bugfixes:
- π #6552: panic: Stop called more than once on ... created by nat.Service
- π #6564: Closing an already removed connection causes GUI error message
- π #6646: Misleading error message when to be deleted dir contains receive-only changes
- π #6653: panic: nil pointer dereference in leveldb.(*DB).isClosed()
- π #6654: panic: runtime error: index out of range in processNeeded()
- β¬οΈ #6655: panic: nil pointer dereference in checkUpgrade()
- π #6679: QUIC listener is not added when default TCP port is unavailable
- π #6697: Malformed listen address causes hang on startup
- π #6706: Changing a folder in web UI removes introduced-by info
β¨ Enhancements:
- π #1830: "Folder path missing" when folder path is a junction
- π #4703: Suggest setting up auth on initial startup
- π #5910: Add Badger database backend for testing and consideration
- β‘οΈ #6372: Reduce database size by optimizing version list storage
Other issues:
-
v1.7.0-rc.1
June 08, 2020 -
v1.6.1 Changes
June 02, 2020v1.6.1
π This is a fixup release on 1.6.0 in order to restore the auto upgrade
critera broken in 1.5.0.π Bugfixes:
- β¬οΈ #6701: Syncthing 1.5.0+ auto upgrades even with auto upgrades disabled in config