Salesforce CLI 2.19.7

Changes

• ~We've added exit codes for many Salesforce CLI command failures to better help you understand what happened. In particular, commands that:changed
• ~We've removed the --json flag of the apex log tail command. Why? Because it didn't make much sense in the first place. The only way to exit the command is to enter Ctrl-C, so the JSON output can't be captured. And don't worry, we checked our telemetry data: this flag is hardly ever used. Get logs in JSON format with the apex list log or apex get log commands.changed
• ~We removed the plugin-login plugin from Salesforce CLI. The plugin contained two general commands, both of which are deprecated: org login and org logout. Use specific commands instead, such as org login web or org login jwt.changed
• ~We converted plugin-packaging from a JIT to a core plugin. This change doesn't fix the root cause of GitHub issue 2540 but should help some users who commented there.changed
• +If you specify Apex tests with the --tests flag of project deploy start|validate, the --test-level flag defaults to RunSpecifiedTests.added
• +Manage source tracking in existing orgs with these two new commands:added
• +Ignore warnings and allow a deployment to validate successfully with the new --ignore-warnings flag of project deploy validate. This flag is similar to the equivalent flag of project deploy start.added
• *Your CLI configuration files are now cross-save safe. Wow! But what does that mean? Well, Salesforce CLI would sometimes try to save 2 copies of the same file concurrently, resulting in either an invalid JSON file or one of the "savers" losing their changes. To fix this issue, we redesigned how files are saved to try to be safer about concurrency. This fix applies to configuration files that...fixed
• *The org login access-token command now honors the SF_ACCESS_TOKEN environment variable, in addition to SFDX_ACCESS_TOKEN. Side note: We encourage you to use the SF_ env vars because the old SFDX_ ones might go away one day. We also fixed the --help for the command to mention SF_ACCESS_TOKEN.fixed
• *The cmdt generate records command now correctly handles CSV files that produce non-unique custom metadata type record names.fixed
• *The project deploy quick command now correctly waits for the quick deploy to finish, and then returns the results of the quick deploy and not of the original validate deploy.fixed
• *If the project deploy start command fails to deploy a component, it now always displays the error along with the name of the failed component.fixed