Files
zero/docs/UPDATE.md
T
Anandan 726f1512a3 Clean up public release docs (#339)
Rewrite the README around the initial public-release user flow, add the logo asset, and refresh install/update documentation.

Remove internal planning, audit, design, and work-split documents from the public docs tree.

Update stale documentation references and workspace seed expectations to point at public docs.

Tested: env GOCACHE=/tmp/zero-go-cache go test ./internal/workspaceseed

Tested: git diff --check
2026-06-28 17:13:21 +05:30

1.4 KiB

Update Flow

zero update --check checks the latest GitHub release and compares it with the local CLI version.

zero update --check
zero update --check --json
zero update --check --repo Gitlawb/zero
zero update --check --target windows-x64

The command is intentionally check-only:

  • It does not replace the running binary.
  • It exits with code 0 when the check succeeds, even when an update is available.
  • It exits with code 1 when the release check cannot be completed.
  • --json prints the same result in a machine-readable format for scripts and CI.

Useful flags:

Flag Purpose
--repo <owner/repo> Check another GitHub repository.
`--endpoint <url owner/repo>`
--timeout <duration> Override the default release check timeout.
--target <platform-arch> Validate release metadata for another supported target.

Supported targets are linux-x64, linux-arm64, macos-x64, macos-arm64, windows-x64, and windows-arm64. Without --target, Zero checks the current platform.

Endpoint resolution order:

  1. --endpoint
  2. ZERO_UPDATE_RELEASE_URL
  3. --repo
  4. https://api.github.com/repos/Gitlawb/zero/releases/latest

Installer scripts download the matching release asset for the local platform and verify its .sha256 file. If Zero is already installed, run zero update --check before reinstalling.