Git commit merge with unwanted ending newline character

Previously, when you commit a metadata component to Git via ClickDeploy, our merge algorithm introduced an unwanted newline character at the end of the metadata file. While this had no semantic implications, it introduced noises as part of the code review process. Our merge algorithm has been updated in this release to address this issue.

Permission set deployments where an object is selected with at least one field not exists in the target organization

Previously, in an org-org deployment flow, when a deployment includes a permission set and a custom object where at least one of the object's fields does not exist in the target organization and is not included in the deployment, the deployment would error due to missing dependencies. This issue has been addressed in this release. ClickDeploy now automatically excludes permissions for fields that are not included in the deployment even when the object is selected.

Did this answer your question?