Runsfdx updateto update the CLI to the latest available version. Installation You can install this by either using an OS-specific installeravailable here, by directly installing it withnpmoryarn(see the instructions below). Installing withnpmoryarn ...
(core)", "@oclif/plugin-update 1.5.0 (core)", "@oclif/plugin-warn-if-update-available 1.7.3 (core)", "@oclif/plugin-which 1.0.4 (core)", "@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)", "alias 2.0.0 (core)", "apex 0.11.0 (core)", "auth 1.8.2 (core)", "community ...
C:\Users\Darrell\AppData\Local\sfdx\client\7.209.6-8ba3197\sf @veauxThanks - I'm not seeing the same on1.86.7-legacy.0. I would try runningsf plugins updateto see if maybe one of your user-installed plugins needs updated deps (specifically @oclif/core). If that doesn't work I wou...
If you want to ensure that you’re running the latest version of Salesforce CLI, you can manually update it.
(core)", "@oclif/plugin-update 4.5.3 (core)", "@oclif/plugin-version 2.2.10 (core)", "@oclif/plugin-warn-if-update-available 3.1.11 (core)", "@oclif/plugin-which 3.2.10 (core)", "@salesforce/cli 2.56.7 (core)", "apex 3.4.2 (core)", "api 1.1.0 (core)", "auth 3.6....
sfdx plugins:install @oclif/plugin-update@3.2.4will replace the plugin that has the bug. You can run thisbefore the CLI deletes itselfto prevent the problem. If the problem already happened, you need on one of the other options.