We have been performing out deployments with a package.xml that had a version of 42.0 and it was metadata API format scaffolding but we are trying to create a new deployment pipeline which will have a a source format. I am trying to change the version setting to 47.0. Is it going to impact anything.Is it going to deploy everything in my org with version 47.0?
Is it going to impact anything. Is it going to deploy everything in my org with version 47.0?
You will be talking to version 47.0 of the Metadata API. Your components must be valid and well-formed as of that API version. However, note that your Apex components' own API versions will not be upgraded.
I tend to see problems with API version upgrades for
package.xml on declarative metadata. When you run your first deploys, you may see errors indicating that specific tags in your declarative metadata have been deprecated and must be removed. For example, the property
CustomTabs is not valid in 47.0, nor
If your metadata contains any properties that were legal on 42.0 and are not on 47.0 (I don't know off the top of my head if that's a non-empty set), you'll simply need to remove them where they're called out in Metadata API errors.