Property 'encrypted' not valid in version 44.0

This situation is caused because the branches have the metadata in API v43 and the Copado backend has changed to the Salesforce API v44 on the 4th of February.

The "encrypted" tag for the custom fields has been deprecated (available until API v43) and a new tag called "encryptionScheme" has replaced it.

The old "encrypted" tag only has 2 values (true or false), whereas the new tag "encryptionScheme" has 4 different values.
The old value "false" can be replaced by "None", but for the old value "true", now there are 3 options (ProbabilisticEncryption, CaseSensitiveDeterministicEncryption, and CaseInsensitiveDeterministicEncryption). The option will vary depending on the type of Encryption you have available for your Org and the specific encryption defined for each custom field.

For this situation, the recommended workaround is as follows:

1.- Open the Git Snapshot record linked to the master branch of your Git Repository and then click on Create Snapshot Now. This way we update the master branch to API v44.
2.- Recreate all feature branches of the User Stories in Progress. You can do this by using the Recommit + Recreate feature in the user story. More information here: Recommit files.
3.- Recreate the Promotion branches that are in Progress. Navigate to the Promotion records that are in progress and create the deployment again to generate a new promotion branch.
4 .- Deploy the promotion.

Alternatively, you can use the "Find and Replace" functionality to safely replace the <encrypted>false</encrypted> tag with <encryptionScheme>None</encryptionScheme>. However replacing the true option <encrypted>true</encrypted> can be risky (potential data loss) if the replaced values is not the one set in the field on Salesforce. We do not recommend to do the find and replace for the <encrypted>true</encrypted> tag. If you do so, be aware that there can be unexpected results and you will do it at your own risk.

How did we do?