DiffersToHighestOrLowestSemverMinor
When this happens
- ✓ Instance is in a Same Minor version group with
preferVersionset - ✓ All instances share the same MAJOR version
- ✘ Instance's MAJOR.MINOR is not the highest (or lowest) MAJOR.MINOR in the group
How it's fixed
The instance is updated to match the preferred MAJOR.MINOR target. The range selection follows this priority:
- If instance has a With Range semver group with a preferred range which will not allow a version outside of the MAJOR.MINOR range to be installed, then use the preferred range
- If instance has no semver group and on-disk range does not allow a version outside of the MAJOR.MINOR range to be installed, then preserve the on-disk range
- Otherwise use
~(Same Minor policy wins over unsafe ranges)
Safe ranges are "" (Exact) and ~ (Patch).