Updating

LazyTeams ships a built-in self-updater, so you can upgrade the TUI and its auth helper without manually downloading release assets.

Update command

lazyteams --update

--update compares the running version against the latest GitHub release. If a newer release exists, it:

1. Prints which release is available and asks for confirmation.
2. Downloads the lazyteams and lazyteams-auth binaries for your platform (Linux, macOS, or Windows; amd64 or arm64).
3. Verifies each binary against the release's published SHA256SUMS before touching anything.
4. Replaces the running binaries and restarts the app.

If you are already on the latest version it reports Already up to date and exits.

Requirements & notes

• Versioned builds only. A binary built directly with go build reports dev as its version, and --update always considers any release newer than dev. Build with make build VERSION=vX.Y.Z or install a release binary for the comparisons to be meaningful.
• Writable install location. The binaries must be in a directory your user can write to (for example ~/.local/bin, not /usr/bin unless you own it).
• Network access to github.com is required.
• Both binaries are updated together. The auth helper is found next to the TUI binary as lazyteams-auth (or lazyteams-auth.exe on Windows).

Integrity & trust

Every download is fetched over HTTPS and must resolve to a GitHub host. Each binary is checked against the SHA256SUMS shipped in the same release; the updater refuses to proceed if that file is missing, and aborts on any checksum mismatch.

Note: this is transport integrity, not full code-signing. The checksum is published alongside the binaries it protects, so treat --update output as trusted only if you already trust the release author. See Security.