Updates and version picker: startup check, install, pin a build

Senzoukria desktop checks for a new version at startup and offers to install it. The Versions card on the Account page lists every published build, lets you install any of them, and can pin a build so the auto-updater stops moving you forward.

Senzoukria · Documentation · Updated September 2026


Where to find it

Where
Update modal at startup; Account → Versions card for the picker; Settings → About shows the version
Skipped when
Running from sources (development build) or when a version is pinned
Safety
Signatures are verified before anything runs; a build without a published signature is listed as "unavailable"

What it does

At startup, once the session is restored, the app asks the update server for a newer version. If one exists, a modal "Update available" shows the new version, the running version and the release notes, with two buttons: "Install now" and "Remind me later". Installing downloads with a progress bar and relaunches the app. Network errors, outages or a missing signature on the latest release never block the start: the check is simply reported as done.

The Versions card is the manual side of the same mechanism. It lists the published builds with their date and size, marks the running build "Running", and lets you install any other one. Everything sensitive stays on the Rust side: URL resolution, signature verification, the installer launch.

Versions card

Controls and states
ControlState or defaultWhat it does
InstallShown on every installable build that is not runningOpens a confirmation with three choices
Install & pinConfirmation choiceInstalls that build and pins it: automatic updates are off until you resume them
Install onlyConfirmation choiceInstalls that build; the auto-updater may move you forward again at the next launch
CancelConfirmation choiceCloses the confirmation
Pinned {version} badgeAbsent by defaultShown in the card header while a pin exists, with the note "Automatic updates are off while a version is pinned."
Resume automatic updatesLink in the pin noteRemoves the pin
unavailableBuilds without a published signatureCannot be installed from the app
ProgressPercentage during a downloadUpdated by the download loop every 512 KB

How to use it

To roll back after a bad release, open Account → Versions, click Install on the previous build and choose "Install & pin". The app closes, the Windows installer runs, and at the next launch the startup check is skipped because of the pin. When the fix ships, click "Resume automatic updates" or install the newer build directly.

If the card says the running build is not the pinned one, the install did not complete; run it again or resume automatic updates.

The installed version is printed on the Welcome footer, the Account footer and the About page; the release notes are behind "What's new" on the Welcome screen.

Limits or pitfalls

Things to know before installing:

  • Installing closes the app: the installer must replace binaries that are locked while it runs.
  • A development build launched from sources never checks for updates; a working branch is always behind the published version, and the prompt would return at every start.
  • An empty pin value counts as no pin, so a blank preference cannot silently freeze updates.
  • If reading the pin fails, the check proceeds: a broken preference must not stop everyone's updates.
  • The picker sends only a version string to the Rust side; the download address is resolved server-side.

This page in other languages

Frequently asked questions

I rolled back and the app updated itself again. Why?
You chose "Install only". Use "Install & pin" so the startup check is skipped until you resume automatic updates.
Why is a build marked unavailable?
No signature was published for it. The app refuses to install a build it cannot verify.
Why does my local development build keep asking to update?
It should not any more: the check is skipped for development builds since 2026-09-10. Update the checkout if the prompt still appears.

Keep reading