Here are the new and changed features in recent updates of Salesforce CLI and the
sfdx version to display the version of Salesforce CLI installed on your computer. Run
sfdx plugins --core to display the version of the installed
sfdx update to update both the CLI and the
salesforcedx plug-in to the latest available version.
Click here for the v46 release notes.
Welcome to the first release of version 47 of the
salesforcedx plug-in for Salesforce CLI in Winter '20. Here's what's changed:
force:org:createcommand encounters signup errors, Salesforce CLI no longer hangs.
force:org:createcommand encounters problems with streaming, it fails over to the polling client, and the command timeout default (or the
--waitparameter value) is now honored.
source:statusrecognize the remote changes.
sfdx force:source:retrieve -x package.xmlor
sfdx force:source:retrieve -m Dashboard:Dashboard_Folder/Dashboard_Nameto retrieve your dashboard. If you plan to retrieve using a manifest, make sure to add dashboards to your
force:source:deletedeletes an entire directory. To delete an individual file, delete it from your local DX project, then use
force:source:push(for scratch orgs) or
force:source:deployto update the static resource in the target org.
We're still working on creating
salesforcedx v47 installers. However, you can easily update Salesforce CLI to v47 by running
sfdx update or any CLI command. If you are installing Salesforce CLI for the first time, see Install Salesforce CLI to install the CLI for your operating system, then run
If you installed the pre-release version 47 of the
salesforcedx plug-in, uninstall it, then run the update command.
sfdx plugins:uninstall salesforcedx sfdx update
These new commands are now available in
salesforcedx v47 (beta).
force:package:hammertest:list: Lists the statuses of running and completed ISV Hammer tests.
force:package:hammertest:report: Returns the status of a running ISV Hammer test or the results of a completed hammer test.
force:package:hammertest:run: Runs ISV Hammer for the specified package version and subscriber orgs.
Note: As a beta feature, ISV Hammer is a preview and isn’t part of the “Services” under your master subscription agreement with Salesforce. Use this feature at your sole discretion, and make your purchase decisions only on the basis of generally available products and features. Salesforce doesn’t guarantee general availability of this feature within any particular time frame or at all, and we can discontinue it at any time. This feature is for evaluation purposes only, not for production use. It’s offered as is and isn’t supported, and Salesforce has no liability for any harm or damage arising out of or in connection with it. All restrictions, Salesforce reservation of rights, obligations concerning the Services, and terms for related Non-Salesforce Applications and Content apply equally to your use of this feature. You can provide feedback and suggestions for this feature in the ISV Hammer group in the Trailblazer Community.
These new commands are available in
force:auth:device:login(beta). You can authorize an org using a device code. This means that you can use Salesforce CLI to authenticate in a Docker container or any headless environment without setting up JWT. For more information, see OAuth 2.0 Device Authentication Flow in Salesforce Help or Remote Development in the Salesforce Extensions for Visual Studio Code User Guide.
force:auth:device:login command is in beta and has been released early so we can collect your feedback. It may contain significant problems, undergo major changes, or be discontinued. If you encounter any problems, or want to request an enhancement, open a GitHub issue. The use of this feature is governed by the Salesforce.com Program Agreement.
These parameters are new in
force:package:hammertest:run --apextestinterface | -n (beta). After upgrade validation, runs the Apex tests in the subscriber org that implement this interface.
force:package:version:create. We added several parameters to this command:
|Calculates and stores the code coverage percentage by running the Apex tests included in the package version. To promote a new managed package version to the released state, the code coverage minimum must be met.|
|For managed packages only, specifies an Apex script to run automatically in the subscriber org after the managed package is installed or upgraded.|
|Specifies a URL to post-install instructions for subscribers.|
|Specifies a URL to release notes.|
|For managed packages only, specifies an Apex script to run automatically in the subscriber org before the managed package is uninstalled.|
The functionality for these commands changed in weekly releases of
salesforcedx v46 or in the pre-release of v47.
force:org:delete -u MyDevSandbox. Deleting a sandbox created by the CLI is now supported.
force:package:install --securitytype | -s. We changed the default value changed from AllUsers to AdminsOnly.
force:source:pull. Source tracking is supported for Einstein Bots metadata in scratch orgs.