Salesforce CLI 2.35.6

Changes

• ~As previously announced, Salesforce CLI is now using a major new version of oclif/plugin-plugins; this oclif plugin uses npm instead of yarn (v1) to install and update user plugins.changed
• +Specify the flag values for Salesforce CLI commands in local text files by using the --flags-dir <dir-name> flag when running the command. If the command finds a file in the specified directory with the same name as one of its flags, it uses the contents of the file as the value of the flag. Take this command, for example:added
• *You can now include the same source component in all the manifest files (standard, pre-deploy-delete, post-deploy-delete) simultaneously. As a result, you can now, for example, first delete a component and then add it again in a single execution of the project deploy start command.fixed
• *Salesforce CLI now supports authenticating to orgs with .cn domains.fixed
• *You can now use the --target-org flag with the project deploy cancel command. (GitHub discussion #2300, plugin-deploy-retrieve PRfixed
• *If you run a non-existent command with "closed stdin" (i.e. you specify <&- or < /dev/null after the command), Salesforce CLI now waits 10 seconds after prompting for a matching command, and then returns the appropriate error exit code. Previously it returned a 0 exit code. oclif GitHub issue [#266, oclif plugin-not-found PRfixed
• *We've improved the performance and output messages for many of the data commands. In particular:fixed