Updating Flosum CLI and DevOps-CLI Extension

Known Issues: Required Update

An update is required. The current release of Flosum DevOps requires the latest versions of the Flosum CLI (@flosum/cli package) and the Flosum DevOps-CLI Extension. Earlier CLI releases do not support topologies and cannot work with a DevOps tenant that uses them, so existing installations must be updated.

Node.js 22 is required. On Node.js 24, the install and update commands appear to succeed but leave you on an earlier release. Move to Node.js 22 before installing or updating.

Operating System Compatibility

Flosum CLI and Flosum DevOps-CLI Extension are compatible with the following operating systems:

• macOS
• Linux

These tools are currently not designed to work with Windows.

Overview

This article explains how to update an existing Flosum CLI installation to the latest release.

The Flosum CLI stays on the version you installed until you run the update command, so a working installation can become outdated without any indication that a newer release exists.

Updating uses the same command as installing. However, you should check your Node.js version before running it.

Confirm Your Node.js Version Before You Update

Run node --version and confirm it reports v22.x before updating anything.

On any other version of Node.js, the update command will replace your working installation with an older release without reporting any errors.

Before You Update

Full prerequisite instructions are in the installation article.

• Installing Flosum CLI Node.js Package

1

Note Your Flosum CLI Version

1. Record the version you are updating from:

   flosum --version

2. Check the latest published release:

   npm view @flosum/cli version

If both report the same version, you are already up to date, and no update is needed.

2

Confirm Node.js and npm

1. Run the following commands:

   node --version
   npm --version

2. Confirm that node --version reports v22.x and that npm --version reports 10.x.
3. If either is different, correct it before continuing. The installation article explains the Node.js and npm prerequisites.

3

Confirm the Build Tools Are Still Present

The Flosum CLI includes a native component. When a release changes that component, the update recompiles it and needs Python 3 and a C++ compiler.

1. Confirm Python 3 is available:

   python3 --version

2. Confirm the C++ compiler is still installed.

Keep the build tools installed. Not every update recompiles the native component, but the ones that do will fail without them.

Updating the Flosum CLI

1

Run the Update Command

1. Open a terminal.
2. Run the same command used to install the CLI:

   npm i -g @flosum/cli

3. Wait for the command to finish. It reports the number of packages it changed, for example changed 1656 packages.

An update is usually faster than a first installation. Expect it to take longer when the release changes the native component.

2

Verify the Update

1. Run the following commands:

   flosum --version
   npm view @flosum/cli version

2. Confirm that both report the same version.

If flosum --version still reports the earlier version, the update did not take effect. See Troubleshooting.

Updating the Extension

The Flosum DevOps-CLI Extension is installed and updated separately through Visual Studio Code, rather than through this command.

1. In Visual Studio Code, open the Extensions view.
2. Select Flosum DevOps-CLI Extension and confirm that no update is available.

The extension and the Flosum CLI each have their own version number. The two numbers are not the same and are not meant to match, so check each one against its own source. Compare the CLI against npm view @flosum/cli version, and check the extension for an available update in Visual Studio Code.

• Installing Flosum DevOps-CLI Extension

Troubleshooting

The update reports success but flosum --version is unchanged

The update command installed an older release, which npm does when your Node.js version does not match the one required by the latest release.

1. Run node --version.
2. If it does not report v22.x, install Node.js 22 as described in the installation article.
3. Run the update command again.
4. Compare flosum --version against npm view @flosum/cli version once more.

The update fails with a build or compiler error

The release changed the native component, so the update tried to recompile it and the build tools are missing or incomplete.

1. Complete the Build Tools prerequisite in the installation article.
2. Remove the partial installation using the cleanup steps in that article.
3. Run the update command again.

A failed update leaves the same partial installation as a failed first installation, so the same cleanup applies.

• Installing Flosum CLI Node.js Package

The flosum command stops working after an update

The update did not finish, leaving the command shortcuts in place without the files they point to.

1. Remove the installation completely using the cleanup steps in the installation article.
2. Confirm that flosum --version reports command not found.
3. Install the CLI again.