aio-cli version not upgrading

Question

hi all,

my aio-cli version is not upgrading even after running the command "npm install -g @adobe/aio-cli"

Here's the log below -

nkrish@SYSMACH io runtime action % npm install -g @adobe/aio-cli
npm warn deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm warn deprecated readdir-scoped-modules@1.1.0: This functionality has been moved to @npmcli/fs
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated debuglog@1.0.1: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated read-package-json@6.0.4: This package is no longer supported. Please use @npmcli/package-json instead.
npm warn deprecated npmlog@5.0.1: This package is no longer supported.
npm warn deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs
npm warn deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs
npm warn deprecated @oclif/screen@3.0.8: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported
npm warn deprecated npmlog@6.0.2: This package is no longer supported.
npm warn deprecated npmlog@6.0.2: This package is no longer supported.
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated are-we-there-yet@2.0.0: This package is no longer supported.
npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.
npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
npm warn deprecated gauge@3.0.2: This package is no longer supported.
npm warn deprecated gauge@4.0.4: This package is no longer supported.
npm warn deprecated gauge@4.0.4: This package is no longer supported.
npm warn deprecated fstream@1.0.12: This package is no longer supported.
npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead

added 48 packages, and changed 1772 packages in 1m

285 packages are looking for funding
run `npm fund` for details
nkrish@SYSMACH io runtime action % npm -v
11.5.2
nkrish@SYSMACH io runtime action % aio -v
› Warning: @adobe/aio-cli update available from 10.3.3 to 11.0.0.
› Run npm install -g @adobe/aio-cli to update.
@adobe/aio-cli/10.3.3 darwin-arm64 node-v23.9.0

giuseppebaglio · Accepted Answer

Here are some practical steps to resolve this.

1) Multiple versions of @adobe/aio-cli may be installed globally or in different locations. Run this command to see all globally installed inbound versions:

npm list -g --depth=0

If you see multiple entries or old versions, remove them:

npm uninstall -g @adobe/aio-cli

2) Sometimes, npm caches packages or leaves broken links:

npm cache clean --force
npm install -g @adobe/aio-cli

3) If aio -v still reports the old version:

Check which aio executable is running:

which aio

Make sure this points to the correct (recently installed) global NPM bin directory. If not, you may have a path to an old copy (sometimes in /usr/local/bin/aio or similar). Remove any old or rogue executables:

rm /path/to/your/bin/aio

4) After cleanup, re-run the install:

npm install -g @adobe/aio-cli

Extra - Node Version Compatibility:

You’re using Node v23.9.0 — very new versions of Node sometimes create npm compatibility issues. If the above fails, consider trying with an LTS Node version (like v20.x or v18.x), using Node Version Manager (nvm):

nvm install 20
nvm use 20
npm install -g @adobe/aio-cli

Extra - Node Version Compatibility:

You’re using Node v23.9.0 — very new versions of Node sometimes create npm compatibility issues. If the above fails, consider trying with an LTS Node version (like v20.x or v18.x), using Node Version Manager (nvm):

Extra - Node Version Compatibility:

You’re using Node v23.9.0 — very new versions of Node sometimes create npm compatibility issues. If the above fails, consider trying with an LTS Node version (like v20.x or v18.x), using Node Version Manager (nvm):

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded