Skip to content
Docs

vercel upgrade

The vercel upgrade command upgrades the Vercel CLI on your machine to the latest version published to npm. It detects which package manager you used to install the CLI and runs the corresponding upgrade command. You can also use this command to enable or disable automatic updates.

If vercel upgrade can't detect a supported global package-manager installation, it exits with an error. Update the CLI with the package manager that installed it. Use vercel upgrade --dry-run to inspect the upgrade command before running it.

terminal
vercel upgrade

Upgrade the Vercel CLI to the latest published version.

terminal
vercel upgrade

Upgrade the Vercel CLI to the latest published version using the package manager that installed it.

terminal
vercel upgrade --dry-run

Print the command that would be executed without making any changes.

terminal
vercel upgrade --autoupdate

Opt into automatic Vercel CLI updates for future releases.

terminal
vercel upgrade --no-autoupdate
Opt out of automatic updates.
terminal
vercel upgrade --json

Emit the upgrade plan as JSON. Implies --dry-run; no upgrade is performed.

terminal
vercel upgrade 59.11.7

Install an exact Vercel CLI version. Use the full major.minor.patch version.

terminal
vercel upgrade latest

Use this when your package manager's minimum release age blocks the newest release. Your package manager installs the newest release that its settings allow.

These are options that only apply to the vercel upgrade command.

The --dry-run option prints the upgrade command that would be executed without running it.

terminal
vercel upgrade --dry-run
Show what would happen, without actually upgrading.

The --autoupdate option turns on automatic CLI updates for future releases:

terminal
vercel upgrade --autoupdate
Enable automatic updates.

The --no-autoupdate option turns them off:

terminal
vercel upgrade --no-autoupdate
Disable automatic updates.

Both options change the setting only and don't run an upgrade.

npm and pnpm can hold back a package release until it reaches a minimum age. If that setting blocks the newest Vercel CLI release, vercel upgrade doesn't install it. It shows you two options: keep the check or skip it.

To keep the check, run vercel upgrade latest. Your package manager installs the newest release that its settings allow.

To skip the check and install the newest release, use the --bypass-min-release-age option:

terminal
vercel upgrade --bypass-min-release-age

Upgrade to the newest release without the package manager's minimum release-age check.

The CLI remembers this choice for later upgrades that you run. Automatic updates always follow your package manager's settings.

To turn the check back on, use the --no-bypass-min-release-age option. It changes the setting only and doesn't run an upgrade:

terminal
vercel upgrade --no-bypass-min-release-age
Turn the minimum release-age check back on.

The --bypass-min-release-age option works only when you installed the CLI with npm or pnpm.

The --json option emits the upgrade plan as JSON. This implies --dry-run, so no upgrade is performed.

terminal
vercel upgrade --json

Output the upgrade plan as JSON for scripting or agent workflows.

The following global options can be passed when using the vercel upgrade command:

For more information on global options and their usage, refer to the options section.

Last updated June 9, 2026

Was this helpful?

supported.