ZakSync v0.1.0-alpha.3

Added

• Existing Proton Drive desktop sync roots now appear as read-only remote mappings on the main screen.
• ZakSync remote folders under /my-files/ZakSync that are not mapped locally can be linked to a local folder.
• The main status badge now shows a compact CLI version.

Fixed

• Staging now supports Windows paths longer than 260 characters by using Unicode extended-length paths with CreateHardLinkW.
• Temporary staging folder names are shorter to preserve more path capacity.
• Spaces in paths remain literal, and valid Windows folder names containing glob metacharacters are escaped before being passed to the official CLI.
• Staging failures now include the underlying Windows error.

Native /devices mappings are intentionally read-only in ZakSync to avoid conflicting with Proton Drive desktop ownership.

Requirements

• Windows 10 or Windows 11
• .NET 8 Desktop Runtime

Verification

• Tested with a path exceeding the legacy 260-character Windows limit and containing spaces
• Runtime-tested against existing Documents and Workspace mappings on a Proton desktop device
• GitHub Actions build and all 17 tests passed
• SHA-256: 9913238B6A245C05ED231E24A2D40FE090780BE94E9B48D9CC81C79AB55CB054

ZakSync is a third-party application and is not officially supported by Proton.