Updates

The installed app keeps itself up to date from Periskopos’s GitHub Releases.

• It checks 30 seconds after it starts and every 6 hours; Check for updates in the tray menu (or File / the app menu) checks now.
• The update button in the title bar (the arrow, just before Reload) shows the version you’re running and where updates stand: up to date and when it last checked, checking, downloading, ready, or why it couldn’t check. It has Check now, or Restart to update once a version is ready; a dot on it means one is waiting.
• Settings → General → Updates shows the same, with the same button.
• What it did is in the log (File → Show log), lines starting update.

Windows and Linux

The new version downloads in the background and installs when you quit, or straight away with Restart to update in the tray menu.

macOS

An unsigned app can’t replace itself, so you get a notification and Download version … in the tray menu, which opens the release; drag the new app into Applications.

Access

The releases are public, so no token is needed. If one is there (PERISKOPOS_UPDATE_TOKEN in your keys file, GH_TOKEN or GITHUB_TOKEN, or a gh auth login) it’s used too, which a fork kept private needs. Nothing is built into the installer.

A build on this computer (Windows)

For working on Periskopos itself: npm run desktop:dist leaves an installer and its latest.yml in release\win. If that build is newer than the app, each check offers it before looking at Releases, with Restart to update, which runs its installer quietly over the app and starts the new version.

It looks only where PERISKOPOS_LOCAL_BUILDS in your keys file points (your checkout’s release\win, say). A build whose installer doesn’t match the checksum in latest.yml (still being written) isn’t offered.