malv update

Update the MALV CLI to the latest version.

Usage

# Update to latest
malv update

# Check current version and update status
malv update --status

# Disable automatic update checks
malv update --disable

# Re-enable automatic update checks
malv update --enable

Options

Option What It Does
--status, -s Show current version and update availability
--disable, -d Disable automatic update checks
--enable, -e Enable automatic update checks
--help, -h Show help

Output

$ malv update

Checking for updates...
Updated @malv/cli: 1.0.0 -> 1.1.0

If already on latest:

$ malv update

✓ Already on latest version (1.1.0)

Automatic Update Checks

By default, the CLI checks for updates in the background on every command. This check:

When an update is available, you'll see a notification after your command completes:

$ malv env

... (command output) ...

──────────────────────────────────────────────────
  Update available: 1.0.0 -> 1.1.0
  Run malv update to update
──────────────────────────────────────────────────

Disabling Update Checks

If you don't want automatic checks:

malv update --disable

To re-enable:

malv update --enable

The setting is stored in ~/.malv/update-config.json.

Check Status

See your current version and whether updates are available:

$ malv update --status

Current version: 1.0.0
Latest version: 1.1.0
Update available: Yes

Auto-update checks: Enabled
Last check: 2 hours ago

How Updates Work

The CLI is distributed via npm. When you run malv update:

  1. Checks npm for the latest @malv/cli version
  2. Compares with your installed version
  3. Runs npm install -g @malv/cli@latest to update

Manual Update

You can also update manually with npm or yarn:

npm install -g @malv/cli@latest
# or
yarn global add @malv/cli@latest

Version Pinning

If you need a specific version:

npm install -g @malv/[email protected]

Consider disabling auto-update checks if you're pinning versions:

malv update --disable

Related Commands