Who needs conflicts?

Improvements for all users:

• ✨ The client should create fewer conflicts on files as we've improved the
  decision logic when dealing with conflicting local and remote changes. If the
  local content can be found in one of its old versions stored on the remote
  Cozy then the client will overwrite it with the remote content instead of
  creating a conflict.
  If that decision was not the one the user expected then the overwritten
  content can still be retrieved from the remote Cozy via the file's versions.
• ⚡ Fetching new remote changes will now be faster as we've removed some network
  calls that are not necessary anymore.
• 🐛 We fixed a bug affecting sub-directories of sub-directories of directories
  moved on the remote Cozy. These could not be updated from the local filesystem
  anymore, triggering Invalid Metadata errors when the client would try to
  synchronize the local modifications (e.g. a move).
  All directories that were affected will be fixed by a data migration upon
  restart of the client.
• 🐛 During the client's on-boarding process, clicking on the ToS link (or any link
  pointing to a URL ending with .pdf) will open the pointed URL within the
  external browser rather than the on-boarding window.
• 🐛 Network errors during the synchronization of a change should not result in a
  blocked synchronization anymore.
• 🐛 Network errors during a file transfer either from or to the remote Cozy will
  now be handled properly, restarting the transfer until too many errors are
  encountered and the global error handling mechanism takes over.

See also known issues.

Happy syncing!