• v0.2.0 23531b0fa2

    v0.2.0
    Some checks failed
    CI / Swift build, lint, and test (push) Successful in 15s
    Release / Prepare Forgejo release (push) Successful in 2s
    Release / Build macOS package (push) Failing after 8s
    Release / Build Arch Linux package (push) Failing after 31s
    CI / Rust build, lint, and test (push) Successful in 12s
    Stable

    erik released this 2026-09-23 22:28:40 -05:00 | 2 commits to main since this release

    kvshare 0.2.0

    Source: annotated tag v0.2.0, commit 23531b0fa28895f75daca24556556d4544bd668e.

    Changes

    • Mirror unmodified top-row numbers to both machines while either screen has control, using the existing number-mirroring toggle.
    • Preserve ordinary input ownership checks, lock protection, and balanced key releases across handoff, disable, and disconnect.
    • Include the persistent macOS signing and Launch Services fixes made since the last tagged release, 0.1.3.

    Breaking compatibility

    Upgrade the Mac app and Linux receiver together. This release uses wire protocol version 2; protocol-v1 peers cannot connect. The GNOME extension protocol is unchanged.

    Early untagged protocol-v2 builds incorrectly displayed 0.1.6. Replace those builds with these 0.2.0 packages rather than inferring compatibility from the old label.

    Packages and verification

    • macOS: kvshare-macos-0.2.0.pkg
    • Arch Linux x86_64: kvshare-0.2.0-1-x86_64.pkg.tar.zst

    Download the package and its matching .sha256 file. Run shasum -a 256 -c kvshare-macos-0.2.0.pkg.sha256 on macOS or sha256sum -c kvshare-0.2.0-1-x86_64.pkg.tar.zst.sha256 on Linux before installing. Preserve configuration; restart both applications after upgrading.

    The macOS app is persistently Apple-signed, but the installer is unsigned and the app is not notarized. For this release, the macOS package was built locally from the approved tag with the existing Apple identity because release CI cannot resolve its configured signing identity. Its expanded payload passed strict/deep signature verification; signing checks were not weakened.

    The Arch package was built from the same tag on the target Arch-based Linux host. The CI Arch build succeeded but its upload failed CA verification, so both packages and checksums were uploaded through the authenticated Forgejo CLI. TLS verification was not disabled. CI signing-identity and upload-CA configuration still need repair; neither failure was hidden or treated as a successful automated release.

    Downloads