Anandan
442f24c7de
* Remove Bun installer test dependency * Harden installer smoke tests * Stabilize npm wrapper subprocess tests * Make npm wrapper fixture explicit ESM
1.9 KiB
Zero Install Scripts
Zero release archives are published as:
zero-v<version>-linux-<arch>.tar.gzzero-v<version>-macos-<arch>.tar.gzzero-v<version>-windows-<arch>.zip
Each archive must have a matching .sha256 file. The install scripts download both files and verify the checksum before copying the binary.
Maintainers can verify the release directory before upload:
go run ./cmd/zero-release package
go run ./cmd/zero-release verify
verify:release requires every archive in dist/release to have a same-directory .sha256 file whose contents are:
<sha256> <archive-name>
Linux And macOS
From a checkout:
scripts/install.sh
Install a specific version:
ZERO_VERSION=0.1.0 scripts/install.sh
Install to a custom directory:
ZERO_INSTALL_DIR="$HOME/bin" scripts/install.sh
Install from a fork or internal repository:
scripts/install.sh --repo owner/repo
Defaults:
- Repository:
Gitlawb/zero - Version: latest GitHub release
- Install path:
~/.local/bin/zero
Requirements: curl or wget, tar, and shasum or sha256sum.
Windows
From a checkout:
powershell -ExecutionPolicy Bypass -File scripts/install.ps1
Install a specific version:
powershell -ExecutionPolicy Bypass -File scripts/install.ps1 -Version 0.1.0
Install to a custom directory:
powershell -ExecutionPolicy Bypass -File scripts/install.ps1 -InstallDir "$env:USERPROFILE\bin"
Install from a fork or internal repository:
powershell -ExecutionPolicy Bypass -File scripts/install.ps1 -Repository owner/repo
Defaults:
- Repository:
Gitlawb/zero - Version: latest GitHub release
- Install path:
%LOCALAPPDATA%\zero\bin\zero.exe
Updating
Check whether a newer release exists:
zero update --check
For M2, updates are check-only. Re-run the installer to replace the local binary after reviewing the release.