18-LAB / Documentation

Updates

Use stable releases from 18-lab-dev/vosu. The security policy supports only the latest release.

Portable and user-writable installs

ENABLE_AUTOUPDATE = true is the default. At startup, release builds check for stable releases and can install them automatically. The updater checks the selected platform archive against its published SHA-256 digest, stages exactly one root executable, and uses a crash-recoverable helper with rollback.

Turn Settings → General → Automatic updates off, or set:

ENABLE_AUTOUPDATE = false

A launch flag overrides startup installation for that launch:

vosu --update=false
# Enable installation for this launch instead:
vosu --update=true
.\vosu.exe --update=false
# Enable installation for this launch instead:
.\vosu.exe --update=true

The dashboard's Update Vosu action runs the same update path. Use the dashboard served by vosu, not a file-loaded page or mismatched proxy origin.

Do not run the Windows executable from an archive or OneDrive-controlled directory: safe replacement and rollback are unavailable there.

Externally managed installs

When the current user cannot write the executable's directory, vosu treats the installation as externally managed on Linux and Windows. Startup skips update checking and recovery, and Automatic updates is disabled with an explanation. The update action reports that the install is managed by a package manager rather than attempting replacement.

Linux release packages configure no software repository. A normal system upgrade therefore does not fetch a newer vosu release. Download the newer package from GitHub releases and install it with the same apt install ./…, dnf install ./…, or pacman -U … command used in installation. The package manager replaces the installed version.

For vosu-git, update with your AUR helper if available, or rebuild the source recipe from current main. This is a development-branch package, not a stable-release channel.

Manual replacement

  1. Download and verify the new complete archive.
  2. Quit vosu from the tray.
  3. Replace the executable and LICENSE with the new archive's files.
  4. On Linux, run vosu --setup against the replaced executable: replacement removes its file capabilities.
  5. Restart vosu and check the dashboard.

Keep configuration and counter data if you want to retain settings. Their paths are in configuration. For failure diagnosis, see troubleshooting.

Source: automatic updates README and operations runbook.

Edit this page on GitHub