Downloads & updates
Get installers from the project's official GitHub Releases page.
| Application | Stable download | Release notes |
|---|---|---|
| GitCat | Latest stable release | All GitCat releases |
| ClipCat | Latest stable release | All ClipCat releases |
Pick the right file
Expand Assets on the release page. Choose a package for your operating system and processor architecture. Available platforms and formats depend on the project; check its installation guide for requirements.
| System | Package |
|---|---|
| Windows | An .exe installer |
| Debian / Ubuntu | A .deb package |
| Fedora / RPM-based Linux | An .rpm package |
| Other compatible Linux distributions | An .AppImage, when provided |
Files such as .sig and latest.json support automatic updaters; they are not installers. Source code archives are for building a project yourself. Install any required runtimes or system libraries listed in the project's guide.
Package signatures and Windows publisher labels
Both applications verify updater packages with Tauri/Minisign signatures. These signatures are separate from Windows Authenticode signing: the current release workflows do not sign the Windows executables or installers with an Authenticode certificate. Cat Ninth is publisher metadata, not a Windows-verified signing identity, so Windows may show an unknown-publisher or SmartScreen warning.
Running a manually downloaded installer does not perform the application's built-in updater verification. See the GitCat code-signing policy and ClipCat code-signing policy for the documented signing process.
Update an installed app
- Read the new release notes for requirements or migration steps.
- Save your work and finish active tasks before installing or restarting.
- Use the app's built-in updater when available, following its guide. Otherwise, download the latest stable package and follow the project's installation instructions.
Keep the same package format and architecture unless the project provides instructions for switching. Package managers may ask for system authorization.
Stable or nightly?
Use stable releases for everyday work. Releases marked Pre-release, including nightly builds, are intended for testing and may contain unfinished changes. Read their notes before installing and check the project's instructions for returning to a stable version.