Salesforce CLI v48 Release Notes

Here are the new and changed features in recent updates of Salesforce CLI and the salesforcedx plug-in.

Run sfdx version to display the version of Salesforce CLI installed on your computer. Run sfdx plugins --core to display the version of the installed salesforcedx plug-in.

Run sfdx update to update both the CLI and the salesforcedx plug-in to the latest available version.

Click here for the v47 release notes.

48.8.0 (April 2, 2020)

• FIX: We fixed some under-the-hood bugs.

48.7.0 (March 26, 2020)

• FIX: We fixed some under-the-hood bugs.

48.6.0 (March 19, 2020)

• We aren't releasing a Salesforce CLI patch this week.

48.5.1 (March 12, 2020)

• FIX: When running force:data:record:update, you can update a date field to a null value.
• FIX: Apex unit test failures appear in the output when you run force:source:deploy --testlevel.

48.4.1 (March 5, 2020)

• NEW: We added a package.json file to the standard and analytics Salesforce DX templates. To create these templates, run force:project:create --template=standard or force:project:create --template=analytics.
• CHANGE: We are deprecating force:doc:commands:list and force:doc:commands:display. We will remove these commands in v49.0. Instead, run sfdx commands, which produces similar output.
• FIX: We fixed force:user:create --json so it works as expected when assigning permsets.

48.3.1 (February 27, 2020)

• FIX: We fixed some under-the-hood bugs.

48.2.0 (February 20, 2020)

• NEW: We introduced three new commands to offer you Lightning Web Components test functionality.

  • force:lightning:lwc:test:create. Creates a Lightning Web Components test with boilerplate code inside a __tests__ directory.
  • force:lightning:lwc:test:setup. Installs Jest unit testing tools for Lightning Web Components.
  • force:lightning:lwc:test:run. Invokes Lightning Web Components Jest unit tests.

  To learn more about testing Lightning Web Components, read our documentation.

• FIX: When deploying source with the -c | --checkonly flag, errors once again display to the console.

48.1.5 (February 18, 2020)

• FIX: We fixed the npm install sfdx-cli error. (Github issue #304).

48.1.4 (February 17, 2020)

• FIX: Deployments to production using force:mdapi:deploy or force:source:deploy complete as expected. (Github issue #305).

48.1.2 (February 15, 2020)

Welcome to the first release of version 48 of the salesforcedx CLI plug-in in Spring '20.

• CHANGE: Now all JSON output will be sent to stdout. Over a year ago we introduced an environment variable, SFDX_JSON_TO_STDOUT, to move all JSON output to stdout when true. This functionality is now the default. If you rely on parsing errors from stderr when using --json, update your tools and scripts to stdout or set SFDX_JSON_TO_STDOUT to false. You can expect more warnings and errors to be sent to stderr even with --json set. Learn more about this change in our blog post.

Installation Notes

We're still working on creating salesforcedx v48 installers. However, you can easily update Salesforce CLI to v48 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 sfdx update.

Uninstall the Pre-Release Version of the salesforcedx CLI Plug-In

If you installed the pre-release version 48 of the salesforcedx plug-in, uninstall it, then run the update command.

sfdx plugins:uninstall salesforcedx

sfdx update

New Commands

force:analytics:template:create. Allows you to create a simple analytics template in a specified directory.

force:community:create. Creates a community using a template.

force:community:publish. Publishes your Lightning community to make it live. Each time you publish, you update the live community with the most recent updates.

force:community:template:list. Retrieves the list of templates available in your org for creating a community.

New Parameters

force:package:version:create --skipvalidation. Skips validation during package version creation. Skipping validation allows you to create package versions faster, but you can’t promote a package version that was created without validation.

force:source:delete --checkonly. Performs a test deployment (validation) in the non-sourced-tracked org without deleting the metadata. After the validation passes, you can safely delete the metadata using this command.

Changed Commands

force:package:version:list. Displays columns that indicate if the package version has passed code coverage, and the code coverage percentage. We also added columns to indicate the ancestor ID and ancestor version number for the package version's ancestor. Ancestor ID and version number display for package versions created in Spring '20 and later.

Changed Parameters

These parameters were added to the force:source:convert and force:mdapi:convert commands in a weekly release of salesforcedx.

-x | --manifest. Specifies the complete path to the manifest (package.xml) file that specifies the metadata types to convert.

-m | --metadata. Specifies a comma-separated list of metadata component names to convert.

-p | --sourcepath. Specifies a comma-separated list of paths to the local source files to convert (force:source:convert).

-p | --metadatapath. Specifies a comma-separated list of paths to the local source files to convert (force:mdapi:convert).

Deprecated Parameters

We removed the -a short version of the --apiversion parameter. The following commands were affected:

force:apex:class:create

force:apex:trigger:create

force:lightning:app:create

force:lightning:component:create

force:lightning:event:create

force:lightning:interface:create

force:visualforce:component:create

force:visualforce:page:create