2.2.1.1 release notes

 2.2.1.1

• Issue 2061 - The 2022-03-03 Salesforce CLI update to 7.140.0 promoted the previously beta force:source:push and force:source:pull commands to GA. The JSON output of these new commands is incompatible with that of the previous commands and also seems to include some critical omissions. I've filed a bug in the CLI public issue tracker with my findings on the topic. In order to minimize the impact of these changes to IC2 users, though, I'm providing a workaround in IC2 so that the legacy push/pull commands are used if a version of the CLI is installed with the new commands. This workaround should be seamless unless the CLI is updated from a version before 7.140.0 to 7.140.0+ with open projects where a push or pull has already been performed, in which case just closing and reopening these projects will cause IC2 to re-query the CLI for its version number to determine which commands should be used.

  NOTE: If you use both IC2 and the CLI to push/pull metadata for a given project, you must use a consistent set of commands across the two. Due to the aforementioned issues with the new commands, IC2 currently only supports the legacy commands. As a result, you must also use those commands from the CLI, namely force:source:legacy:push and force:source:legacy:pull. I will be actively working with the Salesforce CLI team to provide full support for the new commands in IC2, but until things like deployment error messages and line/column information are included in the new commands' JSON output, it will not be possible to do so. Hopefully those omissions will be resolved quickly by the CLI team so that IC2 can provide full support for the new commands.

• Added automatic detection of another scenario where LWC deployment via the Tooling API would fail incorrectly and deployment should instead be routed to the Metadata API.