Skip to content

Updates

Jump to bottom
meetsu edited this page Jul 11, 2026 · 3 revisions

Updates

accshift checks for a newer version when you launch it. If one is out, you get a prompt asking whether to install. You can skip a version, install later, or install now. Updates are signed by the project, so accshift refuses to install a tampered file.

How it works

  1. On startup the app checks a small file on GitHub that lists the latest version.
  2. If a newer version is available, you see a prompt.
  3. Accepting downloads the new version, verifies its signature, and replaces the installed app. accshift restarts on the new version.

Signatures are checked against the project's public key. A modified or unsigned download is refused.

Windows

  • Update bundle: MSI / NSIS installer.
  • Replaces the installed binary in place. UAC may prompt depending on how accshift was installed.

Linux

  • Native build: tarball update.
  • Flatpak: updates happen through Flathub. The in-app updater is suppressed on Flatpak builds because Flatpak controls package management.

macOS

  • Update bundle: signed .app bundle in a DMG.
  • Replaces the installed app on disk.

Manual updates

Download the latest installer or bundle from the Releases page. Run it; your data stays in the per-user paths described in Security.

Skipping a version

The update prompt has a "Skip this version" action. Skipped versions stay skipped until a newer release shows up.

Disabling auto-updates

There is no in-app toggle today. To prevent the check, block the updater endpoint at the OS firewall level or run a Flatpak build (where the in-app updater is already disabled).

Clone this wiki locally