Upgrading AWF

The awf upgrade command updates AWF to the latest version directly from GitHub releases.

Check for Updates#

awf upgrade --check

This reports whether a newer version is available without making any changes.

Upgrade to Latest#

awf upgrade

Downloads the latest stable release, verifies its SHA256 checksum, and replaces the current binary atomically.

Install a Specific Version#

awf upgrade v0.5.0

Installs the specified exact SemVer release, allowing both upgrades and downgrades. Both 0.5.0 and v0.5.0 are accepted; ranges such as >=0.5.0 are rejected.

Force Upgrade#

awf upgrade --force

Skips version comparison and package manager detection. Required when:

• Running a development build (awf --version shows “dev”)
• Binary is installed via a package manager (homebrew, snap, nix)
• You want to reinstall the same version

Authentication#

GitHub API has a rate limit of 60 requests/hour for unauthenticated users. For higher limits:

export GITHUB_TOKEN=ghp_your_token_here
awf upgrade --check

AWF also tries gh auth token automatically if the GitHub CLI is installed.

Flags#

Troubleshooting#

Permission Denied#

If you see a permission error, the binary directory is not writable:

sudo awf upgrade

Package Manager Warning#

If AWF was installed via homebrew, snap, or nix, awf upgrade will warn you. Use your package manager instead, or pass --force to override.

Dev Build#

Development builds (compiled from source) cannot determine their version. Use --force:

awf upgrade --force

See Also#

• Commands — CLI command reference
• Workflow Packs — Installing and managing workflow packs
• Plugins — Plugin installation and management