This is a regular periodic release recommended for all users.
#3935: Leading and trailing spaces are no longer stripped in the GUI password field
#3908: The GUI shows remaining amount of data to sync per folder.
#3933: There should no longer be empty entries in the global log
#3938: Weak hashing is now by default only enabled when it makes sense from a performance point of view. Also
This release introduces the the ability to choose between stable and candidate releases for auto upgrades. See also:
A while back we used to release once a week. Since this summer releases are made every second Tuesday. We will now introduce the concept of "stable releases" and "release candidates".
A new release candidate will be released every two weeks, based on the current state of development. That's pretty much what we've always been doing. The difference is that it will then be in testing for about two weeks before being promoted to stable release status.
You can read more about the details in
I notice that
#3938 has slipped into the release without hitting a release candidate.
Policy v Pragmatism?
The first RC was not a real RC, I just needed one to ensure that it was possible to release RC:s and that the 0.14.22 real release would be able to upgrade to them.
I may have missed something, but I don’t see the binary releases for v0.14.22 on the Github Releases page. I see them for the RC, but not the released version. Are we getting those elsewhere now?
I pulled back this release due to
Today Syncthing was not running on my servers, found this in logs
2017/02/07 11:39:30 INFO: Automatic upgrade (current "v0.14.21" < latest "v0.14.22")
2017/02/07 11:39:34 WARNING: Automatically upgraded to version "v0.14.22". Restarting in 1 minute.
2017/02/07 11:40:34 INFO: Exiting
Manual start was necessary. No errors found, all seems to work as usual, no prior changes in config/network/user permissions, etc. Happened on multiple computers (one of them with manual update) Only simi…
and will post a v0.14.23 once this is solved. It “only” affects users running syncthing manually, without a service manager. Nonetheless, it’s better to pause the upgrading for those not yet on v0.14.22 and allow them to get a fixed version directly.
Man, auto upgrade issues are the worst. Sorry.
v0.14.23 is now out and contains a fix for this.
It’s awesome how we celebrate the new release candidate process by immediately proving the need for it, before it has time to become effective.