Segregate metadata changes due to SFDC release
If I compare my production org to a preview sandbox that has been upgraded to the new release, I see some changed, new, and deleted items that appear to be due to the upgrade. For the most part it probably doesn't make sense (or isn't possible) to deploy those differences in either direction, so it would be nice to be able to exclude them or have them flagged somehow.
For example, in Winter '20 several fields were added to the OpportunityContactRole object. They show up as custom fields in the comparison. If I try to deploy them to production, the Problem Analysis correctly detects them as "Some standard objects or standard fields which don't exist in the target..." and advises me to remove them from the deployment. I'm just wondering if the comparison could see the API difference and filter or separate out anything that's a result of the SFDC upgrade.
Definitely low priority; just wanted to get the idea out there.