KeyPlus packaging and platforms

KeyPlus 0.3 targets Windows and Linux. macOS is not currently supported. The repository contains build configuration for source installs, Debian packages, a strict Snap, and a Windows installer. A build workflow proves that a format can be built; it does not by itself prove that a 0.3 artifact is publicly available.

Source installation

Python 3.10 or later is required. Installing the project provides keyplus and keyplus-gui entry points. PySide6 is currently a normal dependency, so the source package includes both interfaces rather than a CLI-only dependency profile.

Debian

The tag-driven Debian workflow builds an amd64 PyInstaller onedir application and wraps it in a keyplus Debian package. It installs the frozen payload under /usr/bin. The resulting console executable can launch the CLI normally or the GUI with --gui.

The current repository workflow does not install a desktop entry, icon, or AppStream metadata. It should not be described as a fully integrated desktop package until those assets exist and the package has been tested accordingly.

Snap

The committed snap/snapcraft.yaml is the authoritative strict-confinement Snapcraft project for amd64. It exposes keyplus and keyplus-gui, uses the GNOME extension, and requests home for user-selected files and explicit legacy migration. It does not request a network plug.

Canonical’s Snap Store build service is linked to the repository and builds from main. GitHub Actions independently builds the committed manifest for pull requests, reusable workflow calls, or manual validation; it does not hold Store credentials or publish Store revisions. A Canonical build is not the same as a revision being released to a public Store channel.

Snap vault data uses $SNAP_USER_COMMON/KeyPlus, which is shared across Snap revisions rather than tied to one revision’s writable directory.

Windows

The tag-driven Windows workflow creates separate PyInstaller console and windowed payloads, then packages them with the custom KeyPlus installer. The installer verifies staged payload checksums and installs per-user shortcuts; the GUI shortcut targets the windowed payload.

Vault semantics do not depend on the package layout. Source and packaged Windows launches resolve the default vault beneath %LOCALAPPDATA%\ZFordDev\KeyPlus.

Updates and public availability

KeyPlus has no application-managed updater. Snap refreshes are managed by Snap, and other formats require their distribution or installation workflow. Consult the official release and Store listings to determine which version is actually public. Do not use the presence of a workflow, manifest, or installer source as evidence that a current binary has been released.