Before Go 1.21, the initial release of a Go toolchain was
version 1.N, not 1.N.0, so for N < 21, the ordering is
adjusted to place 1.N after the release candidates.
Go changed its versioning scheme in 1.21 from <major>.<minor> to <major>.<minor>.<patch>. CodeQL analysis flags this stating the lack of a patch number "may cause some go commands to fail."
Motivation and Context
CodeQL Analysis warns that some tooling may break without the patch number.
How Has This Been Tested?
It has not been; other than CI.
Types of changes
[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Go changed its versioning scheme in 1.21 from
<major>.<minor>
to<major>.<minor>.<patch>
. CodeQL analysis flags this stating the lack of a patch number "may cause somego
commands to fail."Motivation and Context
CodeQL Analysis warns that some tooling may break without the patch number.
How Has This Been Tested?
It has not been; other than CI.
Types of changes
Checklist: