How to Migrate Your Repository to a New Metadata API Version

Updated 1 week ago by Copado Solutions

Salesforce releases three new versions throughout the year, Winter, Spring and Summer. These releases include changes in the Metadata API as new functionality is added, while some metadata items are deprecated or removed.

If you are not using any of the metadata types affected by Salesforce's new release, you may not need to make any updates or adjustments. However, what if you want your repository to be in the latest version of Salesforce's Metadata API? Keep reading to learn how you can migrate your repository to a new API version.

If you would like to migrate your repository to the latest version of the Metadata API, follow one of the two approaches below:

  1. Use a "fake" deployment and let Copado do the rest:
    1. Commit the elements which have changed in the latest API version on a user story in the lowest environment in your pipeline.
    2. On the same user story, commit an element that has not changed in the org, or something that can be deployed without causing any issues, a label for instance.
    3. Promote the user story manually.
    4. In the Deployment record, deselect all the elements except for the unchanged metadata type, the label in this case.
    5. Execute the deployment.
    6. Copado will merge the branches and will only deploy the label.
    7. Repeat that for the following orgs.
    8. Recommit and recreate user stories in flight.
    9. Recreate non-deployed promotions.
  2. Commit to highest and merge to lowest manually:
    1. Commit the changes of the latest API version into master.
    2. Merge master manually into the org branch outside of Copado.
    3. Recommit and recreate the current feature branches.


How did we do?