ZakSync v0.1.0-alpha.4

Added

• Opt-in automatic update checks in Connection settings.
• Semantic release-channel handling: alpha builds can advance to newer alpha or stable releases, while stable builds ignore pre-releases.
• Verified in-place update installation and automatic restart.

Update security

• Release metadata is read from the public ZakovAU/ZakSync GitHub Releases API.
• Update assets must be named ZakSync.exe and include GitHub's SHA-256 digest.
• The downloaded executable is hashed before it can run.
• Update URLs must be HTTPS GitHub release URLs.
• Checks are limited to once every 24 hours unless the setting is newly enabled.
• The user is prompted before download, replacement, and restart.

Automatic replacement requires ZakSync.exe to be in a folder writable by the current Windows account.

Verification

• End-to-end tested by replacing alpha.3 with alpha.4 and confirming restart
• Replacement binary matched the verified package hash
• Settings dialog screenshot-checked
• GitHub Actions build and all 20 tests passed
• SHA-256: F021CC7C4101D6516DB76862BC02D9B3A25FC1D9EE0586E1EA162866B974E27B

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

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.

ZakSync v0.1.0-alpha.2

Fixed

• Connect account now opens the Proton authorization page through Windows ShellExecute instead of relying on the CLI's silent best-effort browser launch.
• The authorization status is now a clickable retry link.
• If Windows still cannot open the browser, clicking the link copies the validated authorization URL to the clipboard.
• Closing the connection window now cancels and cleans up an active CLI login process.

Security

Authorization links are parsed from the official CLI's JSON output and must use HTTPS on proton.me or a proton.me subdomain before ZakSync will open them.

Requirements

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

Verification

• Full GUI-to-browser authorization flow tested
• GitHub Actions build and all 14 tests passed
• SHA-256: 92AC024AF16EDE5F07A6BF1B41B37230FF5D3212010B491CD3692259FF4C7563

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

ZakSync v0.1.0-alpha.1

ZakSync is an independent Windows sync utility for selectively pushing local folders to Proton Drive through Proton's official Drive CLI.

This is an alpha pre-release. Keep a separate backup of important data while evaluating it.

Highlights

• Per-folder Git-style exclusion rules with preview
• Manual and scheduled local-to-cloud sync
• Safe remote trash propagation for local deletions
• Pause and resume controls
• Optional Start with Windows and minimized startup
• One-click official CLI download with SHA-512 verification
• Browser authentication with credentials kept by Windows Credential Manager

Requirements

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

Download ZakSync.exe, place it in a permanent folder, and run it. Open Connection to install the official CLI and connect your account.

Verification

• GitHub Actions build and all 13 tests passed
• SHA-256: 93B64020BDC69FE668412371BDDFC9797FA39E5C9AC099DDCC3E88B06F943267

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