Bug
sfdx plugins:update is not upgrading the custom plugin to the latest plugin
It should update to the latest version. See attachment.
$ sfdx version
sfdx-cli/6.42.0-ae478b3cb8 (windows-x64) node-v8.9.4
What is the output of running sfdx plugins --core?
On Mon, Dec 3, 2018 at 6:58 AM Venkat Polisetti notifications@github.com
wrote:
Do you want to request a feature or report a bug?
Bug
What is the current behavior?sfdx plugins:update is not upgrading the custom plugin to the latest plugin
What is the expected behavior?It should update to the latest version. See attachment.
Current sfdx version:$ sfdx version
sfdx-cli/6.42.0-ae478b3cb8 (windows-x64) node-v8.9.4[image: capture]
https://user-images.githubusercontent.com/192425/49377859-39a12b80-f6d9-11e8-8045-fb8786878de1.PNG—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/forcedotcom/sfdx-plugin-generate/issues/45, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAQtcjUgIC7ixXUQgAeijx5nDx5AYV_Sks5u1S3_gaJpZM4Y-owf
.
Here it is:
rpolisetti@ALPH-RPOLISETTI MINGW64 ~
$ sfdx plugins --core
@salesforce/plugin-generator 0.0.13 (core)
@salesforce/sfdx-trust 1.0.8 (core)
@venkat.polisetti/crm-sfdx-plugin 2.0.7
builtins 1.0.0 (core)
salesforcedx 44.9.0 (core)
rpolisetti@ALPH-RPOLISETTI MINGW64 ~
$
@rbergman This seems to be related to the "old" version of the yarn command within the cli-engine module used by sfdx.
To test this I've replaced this.bin with my local yarn installation
in this call
await this.fork(this.bin, args, options);
in this file:
.local/share/sfdx/client/node_modules/cli-engine/lib/plugins/yarn.js
and all plugins have been updated successfully.
This also fixed the error: Warning: Mismatched version in <name> plugin manifest. Expected: X.X.X Received: Y.Y.Y
@amphro Can you please take a look at this?
It looks like @jayree found an issue with yarn bins that are not working with sfdx update.
@venkatpolisetti we are in the process of an update that includes a more recent version of Yarn. This should fix this issue. We will test once the update is done and close this bug once we verify its no longer an issue. The update should be out mid-March
@clairebianchi I am starting to see this this week. Is the mid-March update out yet or is there an updated ETA?
@MarcDBehr The update goes out next Thursday :)