Allow deployments across managed package versions
Gearset does not allow comparisons or deployments of custom metadata on managed packages if the versions are different. We got ourselves in a situation where a package in the sandbox was a higher beta version that we couldn't upgrade to. This required us to do all the field deployments via changsets.
Adding a warning for deployments across managed package versions would be ideal as most changes one would deploy wouldn't necessarily cause any issues.
Corbin Smith
shared this idea
We've added the ability to deploy across managed package versions using the Package Item Version Handling dropdown option within the filter sidebar.
If you have any feedback on this, please let us know!
-
Monica Thornton
commented
I'm not sure if this feature has evolved over time but we are able to deploy if managed package versions are different, however if "Installed Packages" type is included with the namespace and the versions are different, the comparison ignores any objects in that namespace. This is currently the most common training issue and troubleshooting issue the teams I'm working with currently encounter when using Gearset. The fix is simple for us, we have to upgrade the packages to match versions, which is internally a recommended pre-deployment step, however it takes time and is easily missed as our Product team is continuously upgrading Production orgs.
It would be ideal to have some sort of package version detection or intelligence in the Compare step as the batches come in and are displayed, or during the Problem Analysis step, that states 'x Package versions are different, not all metadata may be available in your comparison.' or something similar.