Skip to content
One command to visualize your data

vizb update

Update Vizb to the latest stable release:

Terminal window
vizb update

The command identifies the executable that is currently running before choosing an update method. It does not create an installation receipt or other local metadata file.

Installation Behavior
Linux/macOS installer or official release archive Downloads the matching GitHub release, verifies checksums.txt, and atomically replaces the running binary.
Windows standalone Does not modify the executable and prints the PowerShell reinstall command.
go install Prints go install github.com/goptics/vizb@latest without modifying the binary.
WinGet Prints winget upgrade --id goptics.vizb --exact without modifying the package.
Development or unidentified build Refuses to modify the executable and links to the installation instructions.

Windows standalone self-update is not supported yet. Run the printed install.ps1 command after Vizb exits to install the latest release. WinGet and Go-toolchain installations still receive their package-manager commands.

If a standalone binary is in a system directory such as /usr/local/bin, the update needs permission to create a staging file in that directory. Vizb never elevates privileges automatically.

The update is installed only after the release archive SHA-256 matches its entry in the existing GoReleaser checksums.txt asset. An invalid or missing checksum leaves the current executable unchanged.