Skip to content

flox upgrade command


flox-upgrade - upgrade packages in an environment


flox [<general-options>] upgrade
     [-d=<path> | -r=<owner>/<name>]
     [<package or pkg-group>]...


Upgrade packages in an environment to versions present in the environment’s base catalog.

An upgrade should usually be run after updating an environment’s base catalog with flox-update(1).

When no arguments are specified, all packages in the environment are upgraded.

Packages to upgrade can be specified by either pkg-group name, or, if a package is not in a pkg-group with any other packages, it may be specified by ID. If the specified argument is both a pkg-group name and a package ID, the pkg-group is upgraded.

Packages without a specified pkg-group in the manifest are placed in a pkg-group named ‘toplevel’. The packages in that pkg-group can be upgraded without updating any other pkg-groups by passing ‘toplevel’ as the pkg-group name.

See manifest.toml(1) for more on using pkg-groups.


Upgrade Options

<package or pkg-group>
Install ID or pkg-group to upgrade.

Environment Options

If no environment is specified for an environment command, the environment in the current directory or the active environment that was last activated is used.

-d, --dir
Path containing a .flox/ directory.

-r, --remote
A remote environment on FloxHub, specified in the form <owner>/<name>.

General Options

-h, --help
Prints help information.

The following options can be passed when running any flox subcommand but must be specified before the subcommand.

-v, --verbose
Increase logging verbosity. Invoke multiple times for increasing detail.

-q, --quiet
Silence logs except for errors.


flox-update(1) manifest.toml(1),