When Corepack downloads a new version, it checks if it corresponds to same major as the global cached one, and if it does, it uses the more recent one the next time the global version is used. That should give users a more smoother experience as they won't need to call corepack install -g as often – with this PR, it should be needed only when wanting to use a different major, assuming you work on projects that keep their "packageManager" field up-to-date.
When Corepack downloads a new version, it checks if it corresponds to same major as the global cached one, and if it does, it uses the more recent one the next time the global version is used. That should give users a more smoother experience as they won't need to call
corepack install -gas often – with this PR, it should be needed only when wanting to use a different major, assuming you work on projects that keep their"packageManager"field up-to-date.