• v4.0.1 37401695fd

    elliot released this 2026-07-06 10:32:11 -04:00 | 0 commits to main since this release

    zen-sync v4.0.1

    Bugfix + resiliency patch on the v4.0 baseline. Payload-only — the native deployers
    are unchanged from v4.0; keep using the deployer you already have (verify its signature
    against the OOB fingerprint f1dcd890199e2d7abca2eaa1c0d653ac661cc8f13b4e88954eb1428a0fd4648d
    before running).

    Payload: payload.zsi — signed v23.
    SHA-256: 4f174b455c5e8e0a7589a061d3bd42a4e123ec1cd69a72054dda3b9ea1df12d0
    Verifies against the same embedded payload key as v4.0 (no key rotation).

    Fixes

    • Pins now sync a URL change. Editing a pinned/essential site's URL propagates across
      machines instead of silently doing nothing. (The tab itself isn't force-navigated — the
      stored pin URL updates; use "Reset Pinned Tab" to jump to it.)
    • No more stuck "diverged" on favicons, page titles, or SPA sites (Notion etc.). Icon
      and title differences that used to freeze sync now ride along and converge.
    • Themes/mods install reliably on the receiving machine, and removing a theme removes it
      fleet-wide.
    • Fails gracefully. A record it can't understand is skipped (never read as a deletion) and
      a failed step is retried instead of freezing the whole sync; a corrupt local state can no
      longer poison the shared history for other machines.
    • Better diagnostics. Set zen.sync.logLevel (about:config: debug|info|warn) for
      per-action tracing; the Review panel now shows any held/tolerated items read-only.

    Install

    Re-run your existing deployer and point it at this payload.zsi (anti-rollback accepts v23
    over v22). See INSTALL.md. First verify SHA256SUMS.txt:
    sha256sum -c SHA256SUMS.txt

    Downloads
  • v4.0 b7fdb4f8a5

    zen-sync 4.0 Stable

    elliot released this 2026-06-29 13:58:16 -04:00 | 3 commits to main since this release

    Signed payload + native deployers (Windows self-contained / framework-dependent, macOS .app, Linux). Verify each deployer with its .sig against the deployer-release fingerprint published out-of-band (not on this page). SHA256SUMS.txt covers integrity only, not authenticity. Draft until verification completes.

    Downloads