Salesforce CLI 2.1.7
++++~*********
Changes
- Previously, when deploying metadata, Salesforce CLI allowed you to include multiple files with identical file paths in the ZIP file that's sent to the org to deploy, and the org would deploy them. Crazy, huh. We recently swapped out a library to fix a different issue, and the new library no longer supports that incorrect behavior.changed
- View the package name and version when you run package version create list with the new --verbose flag. The information is displayed in both the human-readable table and JSON results. For example:added
- Specify test formats and destructive changes for the project deploy validate command with these new flags:added
- The JSON output of the sf project deploy validate --json command now contains a deployId property, which is useful if the validation fails and you want the ID to figure out the problem. The ID is in the new data property of the JSON output. For example:added
- Easily determine which records failed to bulk upsert or delete by specifying the new --verbose flag of the sf data upsert|delete bulk commands. If one or more records fail to bulk upsert or delete, the command displays a table with the record IDs and error.added
- Salesforce CLI now detects when you include the word help in a command and asks if you're looking for help information about the rest of the command. For example, if you type sf package install help, the CLI asks if you want help about package install.fixed
- If you run project deploy report --results-dir, the command now uses the new results directory rather than the one from the original project deploy start command, if specified.fixed
- You can now run project deploy validate --metdata-dir outside of a Salesforce DX project.fixed
- Deploy and retrieves when running the project deploy|retrieve commands now correctly show the progress bar by default. (GitHub issues 2276 and 2249, plugin-deploy-retrieve PRfixed
- The project retrieve command now clearly displays the API version it's using for the HTTP request/response (apiVersion) and the metadata shape (sourceApiVersion). See How API Version and Source API Version Work in Salesforce CLI for more information.fixed
- We now display the help for partial commands if Salesforce CLI finds only one possible match. For example, sf project create --help correctly displays the help for project generate because it's the only (aliased) match. Previously you'd get a Command not found. error.fixed
- package:version:create no longer remove Profiles just because they are empty. (GitHub issues #2192/#2218 , packaging PRfixed
2 more lines
- package:version:create was briefly erroring because of a change in the xml2js library. They fixed it and that fixed these commands. If you encounter the issue, uninstall the packaging plugin and run your command again to get the new fixed version.fixed
- Salesforce DX projects now support these metadata types:fixed
14 lines4 added1 changed9 fixedtyped from the source notes