Tags: jpolly168/syncthing
Tags
v0.14.10 This is a minor release recommended for all users. Resolved issues: * syncthing#3623: Display of global and local state is clearer, especially in the presence of ignores. * syncthing#3647: GUI does not show "failed items" unless there are items that have failed. Also: * Fixes to questionmark and asterisk handling in ignore patterns. * Build script can create a snap file. * "Black" theme re-added. * Debugging options for deadlocks.
v0.14.9 This is a minor release recommended for all users. Resolved issues: * syncthing#3651: Documentation PDFs are fixed. * syncthing#3638: German localisation is improved. (As are a couple of others as I forgot to update them the last release.) * syncthing#3619: Browser error on first startup doesn't happen as easily anymore. * syncthing#3664: Syncthing compiles in Go versions older than 1.7 again. * syncthing#3577: Adding folder using Long UNC path no longer causes stack overflow (but don't do that, it's not necessary).
v0.14.8 This is a minor release recommended for all users. The main change here is to handle issues with the new SHA256 implementation introduced in 0.14.7. When using the monitor process (which is the default) crashes will be detected and the new hashing package disabled. A manual selection can also be forced by setting the environment variable STHASHING to either "minio" (the new package) or "standard" (the default Go package). Resolved issues: * syncthing#3613: The monitor process now detects crashes due to the new hashing package and disables it on subsequent launch. * syncthing#3614: The two hash packages are benchmarked on startup and the fastest on is selected. * syncthing#3588: Folders are now correctly shown as out of sync when they miss only deleted files. * syncthing#3578: UPnP handling is corrected in the case where more than one router is detected. * syncthing#3639: Patterns with terminal slash (e.g., "dir/") now correctly ignore directory contents.
v0.14.7 This is a minor release recommended for all users. Improvements in this release include faster (i.e., less CPU intensive) hashing on some Intel and ARM64 CPU:s, a more refined dark theme, CORS headers in the API, and an updated set of default discovery servers. Resolved issues since v0.14.6: * syncthing#3596: Deadlock no longer occurs on device removal
v0.14.6 This is a minor release recommended for all users. Resolved issues since v0.14.5: * syncthing#3496: In sync percentages no longer go negative for large numbers of deleted files. * syncthing#3502: Files that were deleted and then ignored are no longer deleted on other devices that didn't ignore them. * syncthing#3525: Configuration is no moved away when perfoming an upgrade on a full disk.
v0.14.5 This is a minor release recommended for all users. Resolved issues since v0.14.4: * syncthing#3492, syncthing#3493: Completion percentage calculations have been improved. * syncthing#3513: Windows build have been fixed for Go 1.7, and now requires Go 1.7. * syncthing#3517: A zero progress update interval doesn't drive up CPU usage during syncing any more. * syncthing#3516: Virtual modtime handling has been fixed, so that master folders no longer become spuriously out of sync. * syncthing#3529: Temporary index sorting databases are removed from disk at startup, if left over after a hard stop. * syncthing#3509: Discovery server now returns Seen time value in UTC. * syncthing#3511: Discovery server now generates a new key pair when one doesn't exist at startup. * syncthing#3503: Relay server no longer crashes with "send on closed channel". * syncthing#3505: Relay server can open ports using uPNP. * syncthing#3506: Relay server can properly listen on IPv6 only or IPv4 only. * syncthing#3500, syncthing#3530: Automatic upgrade takes more care to not leave temporaries behind or remove the original in case of upgrade failure.
v0.14.4 This is a minor release recommended for all users. Several bugs have been fixed and one enhancement added (high precision time stamps). Resolved issues since v0.14.3: * syncthing#1300: In sync percentage is weighted to folder size, not just average of folder completion. * syncthing#3012: Files with invalid file names for Windows now show up in the list of failed items. * syncthing#3297: Accessibility in the GUI is improved. * syncthing#3305: Timestamps are now compared with up to nanosecond precision and synced with up to microsecond precision, depending on the filesystem in use. * syncthing#3457: Ignores and invalid file names are now handled correctly when delta indexes are being used. * syncthing#3458: Files inside directories with names ending in space are now correctly handled on Windows. * syncthing#3466: Connection switching (relay->direct) no longer causes a crash. * syncthing#3468: Old index databases (v0.11-v0.12 and v0.13) are now properly cleaned away from disk. * syncthing#3470: Syncthing no longer claims a connection was from an ignored device when the device is just unknown.
v0.14.3 This is a minor release recommended for all users. Resolved issues since v0.14.2: * syncthing#3451: Devices no longer get stuck in "out of sync" after a disconnection. * syncthing#3448: Syncthing no longer crashes when a connection is lost before index sending has started. * syncthing#3449: Temporary index databases are now created in the home (config) directory, not the system temporary directory.
v0.14.2 This is a minor release recommended for all users. Resolved issues since v0.14.1: * syncthing#3445: Symlinks are now synced correctly again, after a regression introduced in v0.14.1
v0.14.1 This is a minor release recommended for all users. This release includes "delta indexes", a backwards compatible protocol enhancement. Prior to delta indexes being implemented, full index information was exchanged at every connection start. With delta indexes, only index information that has changed since last contact is transferred. Delta indexes are enabled automatically between 0.14.1+ devices. Resolved issues since v0.14.0: * syncthing#438: Delta indexes are now implemented. * syncthing#3440: Files that grow or shrink during scanning would result in conflicts or inconsistent data after synchronization. This issue was introduced in 0.14.0.
PreviousNext