vers upgrade
Check for and install the latest version of the vers CLI from GitHub releases.Usage
Options
Examples
Check and upgrade
Check for updates only
Already up to date
Include pre-releases
How it works
Theupgrade command:
- Version check: Compares current version against GitHub releases
- User confirmation: Prompts before downloading and installing
- Download: Fetches appropriate binary for your platform
- Verification: Validates download using SHA256 checksums
- Backup: Creates backup of current binary before replacement
- Installation: Replaces current binary with new version
- Cleanup: Removes temporary files and backup on success
Platform support
The upgrade system supports multiple platforms:- macOS:
vers-darwin-amd64,vers-darwin-arm64 - Linux:
vers-linux-amd64,vers-linux-arm64,vers-linux-386 - Windows:
vers-windows-amd64.exe,vers-windows-arm64.exe
Security features
Checksum verification
Backup and recovery
Error handling
Development version
No compatible binary
Checksum mismatch
--skip-checksum (not recommended).
Permission issues
Network failures
Advanced usage
Skip checksum verification
Check pre-releases
Automated workflows
Troubleshooting
Stuck downloads
If download appears stuck, cancel and retry. The command uses a 32KB buffer for progress display.Permission errors
Ensure you have write access to the vers binary location:Manual recovery
If upgrade fails and automatic recovery doesn’t work:Prerequisites
- Internet connectivity to reach GitHub API
- Write permissions to the vers binary location
- Sufficient disk space for download and backup
Common Patterns
Upgrade and verify
Pin to a specific version
vers upgrade always pulls the latest release. To downgrade or pin, re-run the installer with VERS_VERSION:
See Also
- vers status - Check environment after upgrading