Release v3.29.0 (cozy-labs#2133)

Improvements for all users:

- Cozy Notes with photos will be exported as a tar archive instead of
  a simple markdown file. Therefore, the client will now unpack the
  markdown file from the archive when displaying a note in a degraded
  mode (i.e. when you're offline or the actual note can't be found on
  the remote Cozy).
- Error messages will now be properly localized and the document names
  included in some of them should be properly displayed instead of
  their type.

Release v3.29.0-beta.2 (cozy-labs#2132)

Improvements for all users:

- Error messages will now be properly localized and the document names
  included in some of them should be properly displayed instead of
  their type.

Release v3.29.0-beta.1 (cozy-labs#2126)

Improvements for all users:

- Cozy Notes with photos will be exported as a tar archive instead of
  a simple markdown file. Therefore, the client will now unpack the
  markdown file from the archive when displaying a note in a degraded
  mode (i.e. when you're offline or the actual note can't be found on
  the remote Cozy).

Release v3.28.1 (cozy-labs#2122)

Improvements for all users:

- The client will now detect when the connected Cozy has been deleted
  and will show an error message accordingly.
  The synchronization will be stopped until you connect your client to
  another Cozy.
- We've worked on the process which decides if a synchronization error
  needs to be displayed or not to make sure you get alerted with the
  suspended synchronization status only if accompanied with an
  explicit error message.
- In some rare situations where a document that was previously
  synchronized is now only present on one side (i.e. we're in the
  middle of re-synchronizing it) a conflict could be generated if the
  document was modified on that remaining side.
  We've introduced some mitigations to avoid generating those
  conflicts.
- Due to a "bug" in Chromium (i.e. which we use through Electron to
  provide our network stack), some error responses sent by the remote
  Cozy to our file upload requests are transformed into a cryptic
  error which we cannot deal with directly. In such cases, we end up
  interpreting them as unreachable Cozy errors which is misleading to
  you.
  We caught and fixed two of those cases:
  * when sending files larger than the maximum allowed by the remote
    Cozy (i.e. 5 GiB for Cozies hosted by us)
  * when the amount of data sent does not match the expected file size
    (i.e. because the actual local file has grown since last we
    detected a change)
- We'll now consider the propagation of a move to the trash either on
  the local filesystem or the remote Cozy as successful when the given
  document does not exist anymore.
  This will prevent delays during the synchronization process since we
  won't have to deal with retries.

Improvements for Windows users:

- The last modification and last access dates on Windows were not
  precise enough for Cozy Desktop to detect sub-second local
  modifications. This would sometimes lead to `Invalid metadata`
  errors when sending modifications to the remote Cozy.
  We've increased this precision to include milliseconds so we should
  not lose any local modification anymore.

Improvements for macOS users:

- Moving a local document to a folder that was just renamed or moved
  (e.g. a folder that was just created with a custom name) will be
  properly handled and not generate incoherent movements.
- Some steps of the initial scan could be run twice if some local
  modifications were detected while the initial scan was still
  running.
  We've made sure we don't lose time of consume unnecessary computing
  resources by making sure those steps are only run for the real
  initial scan.

Release v3.28.1-beta.4 (cozy-labs#2121)

Improvements for all users:

- We've realized that the errors thrown when trying to trash a missing
  local document would not always be caught because of an unexpected
  message localization.
  We've completely changed the way we catch these errors to not depend
  on their message altogether.

Release v3.28.1-beta.3 (cozy-labs#2116)

Improvements for all users:

- We'll now consider the propagation of a move to the trash either on
  the local filesystem or the remote Cozy as successful when the given
  document does not exist anymore.
  This will prevent delays during the synchronization process since we
  won't have to deal with retries.

Release v3.28.1-beta.2 (cozy-labs#2112)

Improvements for Windows users:

- The last modification and last access dates on Windows were not
  precise enough for Cozy Desktop to detect sub-second local
  modifications. This would sometimes lead to `Invalid metadata`
  errors when sending modifications to the remote Cozy.
  We've increased this precision to include milliseconds so we should
  not lose any local modification anymore.

Improvements for all users:

- Due to a "bug" in Chromium (i.e. which we use through Electron to
  provide our network stack), some error responses sent by the remote
  Cozy to our file upload requests are transformed into a cryptic
  error which we cannot deal with directly. In such cases, we end up
  interpreting them as unreachable Cozy errors which is misleading to
  you.
  We caught and fixed two of those cases:
  * when sending files larger than the maximum allowed by the remote
    Cozy (i.e. 5 GiB for Cozies hosted by us)
  * when the amount of data sent does not match the expected file size
    (i.e. because the actual local file has grown since last we
    detected a change)

Improvements for macOS users:

- Some steps of the initial scan could be run twice if some local
  modifications were detected while the initial scan was still
  running.
  We've made sure we don't lose time of consume unnecessary computing
  resources by making sure those steps are only run for the real
  initial scan.

Release v3.28.1-beta.1 (cozy-labs#2099)

Improvements for all users:

- The client will now detect when the connected Cozy has been deleted
  and will show an error message accordingly. The synchronization will
  be stopped until you connect your client to another Cozy.
- We've worked on the process which decides if a synchronization error
  needs to be displayed or not to make sure you get alerted with the
  suspended synchronization status only if accompanied with an
  explicit error message.
- In some rare situations where a document that was previously
  synchronized is now only present on one side (i.e. we're in the
  middle of re-synchronizing it) a conflict could be generated if the
  document was modified on that remaining side.
  We've introduced some mitigations to avoid generating those
  conflicts.

Improvements for macOS users:

- Moving a local document to a folder that was just renamed or moved
  (e.g. a folder that was just created with a custom name) will be
  properly handled and not generate incoherent movements.

Release v3.28.0 (cozy-labs#2094)

Improvements for all users:

- The client will only trigger one synchronization retry loop when
  encountering an unreachable Cozy error in both the synchronization
  process and the remote watcher very closely.
- New remote documents whose path would be incompatible with the local
  filesystem will not be ignored anymore.
- Local documents who've been moved or renamed remotely to a path that
  would be incompatible with the local filesystem won't be trashed
  anymore.
- Changes that can't be synchronized because the document has an
  incompatible name or path with the local filesystem will now suspend
  the synchronization and an error message will be displayed so you
  can take action.
- Moves for which the destination path is exactly the same as the
  source path will now be treated as modifications rather than
  triggering errors.

Improvements for Windows and macOS users:

- After the remote Cozy has been found unreachable because of a
  network error such as a interface change, the subsequent requests
  won't fail anymore with the same error once a stable connection is
  back.

Improvements for Windows users:

- The client should not create conflicts anymore when propagating on
  Windows the combination of the move/renaming and the modification of
  a Cozy Note (via the Notes web application).
- It seems that paths on Windows created by the Desktop client can
  actually exceed the 259 characters limit. Therefore we've increased
  the limit defined in the client itself to 32766 characters.
  Documents that had been previously found incompatible with the local
  filesystem because of the previous path length limit will be updated
  to take the new limit into account. Most of them should thus become
  compatible.
- Synchronization error messages displayed in the main window will now
  only contain the name of the document involved instead of its
  complete path.

Improvements for macOS users:

- Custom folder icons will now be ignored to avoid blocking the
  synchronization as their name contains a character forbidden on
  remote Cozies.
- The app dock icon should now only be visible when an app window
  other than the main window is open. This should also prevent
  blocking the computer shutdown.

Improvements for Linux users:

- The client won't show a popup error message anymore when
  automatically starting with the computer.

Release v3.28.0-beta.2 (cozy-labs#2092)

Improvements for Windows and macOS users:

- After the remote Cozy has been found unreachable because of a
  network error such as a interface change, the subsequent requests
  won't fail anymore with the same error once a stable connection is
  back.

Improvements for Windows users:

- Documents that had been previously found incompatible with the local
  filesystem because of the previous path length limit will be updated
  to take the new limit into account. Most of them should thus become
  compatible.
- Synchronization error messages displayed in the main window will now
  only contain the name of the document involved instead of its
  complete path.