RustClipSync 0.5.2

RustClipSync Desktop 0.5.2

Fix misleading upgrade prompts when a gateway interrupts clipboard sync.

• Show HTTP 502, 503, 504 and Cloudflare 530 as connection failures. Automatic
  sync retries with backoff and resumes when the server is reachable.
• Reserve the upgrade prompt for explicit protocol incompatibility. When a
  gateway rejects the control WebSocket, the client can fall back to HTTPS.
• Existing pairings work with the current protocol 3 server.

Includes Windows x64 and Linux x86_64 packages for Debian 12, Ubuntu 24.04,
Fedora 43 and Arch, with SHA-256 checksums. The Windows installer is unsigned.

RustClipSync 0.5.1

RustClipSync Desktop 0.5.1

Fix desktop synchronization becoming stuck at "Direction not confirmed by the
server" after a temporary clipboard error, even with bidirectional mode selected.

• Keep the configured session when a clipboard read or write fails. Retry with
  the existing exponential backoff, capped at 30 seconds, preserving direction,
  pairing, pending work and the core's protection against uncertain writes.
• Restore the selected direction, pause and sensitive-content settings whenever
  constructing a live session. An unavailable server leaves the local selection
  intact; the shared core confirms the direction before accessing data.
• Apply the recovery fix to both Windows and Linux. Add native regression checks
  covering all three directions, paused/unpaused states, offline reporting and
  repeated session construction with encrypted state preserved.
• Keep the application display name as RustClipSync, with the version shown
  separately in About.

This is a desktop-only patch. Server 3.0.0, protocol 3, rustclipsync-core 0.4.0 and
the persisted data formats remain compatible. Existing paired devices can upgrade
without re-pairing. Omaclipsync and the Android input method need no update for
this fix.

Includes Windows x64, Debian 12, Ubuntu 24.04, Fedora 43 and Arch x86_64 installers
with combined SHA-256 checksums. Windows installers remain unsigned.

RustClipSync 0.5.0

RustClipSync Desktop 0.5.0

Upgrade together with RustClipSync Server 3.0.0. This release requires wire
protocol 3, with rustclipsync-core 0.4.0. Older clients need server 2.0.0.
Mobile applications and Fcitx input methods are released separately.

• Report send-only, receive-only or bidirectional policy before receiving, and
  report pause separately. Direction changes, reconnects and manual actions keep
  local filters and wait for server confirmation. WSS has authenticated HTTP fallback.
• Use fenced device sessions and server-filtered per-device delivery. Reconnect
  replay is at most the latest eligible message inside the server-configured window;
  the desktop client does not hardcode that window.
• Preserve device identity, encrypted local state/history and sensitive inbox.
  Marked sensitive synchronization and automatic sensitive clipboard writes remain
  off by default. Disabling sensitive synchronization does not block ordinary receives.
• Update the exported shared-core snapshot to the released 0.4.0 source. The core's
  opt-in conflict-recovery API does not silently override desktop conflict policy.
• Fix Windows acceptance around disabled controls, asynchronous settings/history,
  direction confirmation and the sensitive-settings scroll target.
• Publish native Windows x64 plus Debian 12, Ubuntu 24.04, Fedora 43 and Arch x86_64
  installers with combined SHA-256 checksums after platform checks pass.

Windows installers remain unsigned. Linux requires the documented Qt runtime
and desktop clipboard/Secret Service support; GNOME Wayland without data-control
is unsupported. Server plaintext visibility and end-to-end encryption limitations
remain unchanged.

RustClipSync 0.4.0

Use the current RustClipSync HTTP API under /api/..., via rustclipsync-core 0.3.0. Update the server and clients together; earlier endpoint paths are not used. Device pairing, encrypted state and receive cursors remain unchanged. No second transport or protocol-version selector is added.

The Windows and Linux agents consume the same exported shared-core snapshot. Native Windows and Linux adapters retain their existing clipboard, history and sensitive-inbox behavior.