Change Int32 to Int64

[asbjornu]

Change the following properties from Int32 to to Int64 to avoid System.OverflowException on int.Parse() of very large numbers:

• SemanticVersion.Major
• SemanticVersion.Minor
• SemanticVersion.Patch
• SemanticVersionBuildMetaData.CommitsSinceTag
• SemanticVersionBuildMetaData.CommitsSinceVersionSource
• SemanticVersionBuildMetaData.UncommittedChanges
• SemanticVersionPreReleaseTag.Number

Related Issue

Fixes #2715.
Fixes #2915.
Fixes #2390.

Motivation and Context

Large numbers in a version number may cause the following lines to throw a System.OverflowException:

GitVersion/src/GitVersion.Core/VersionCalculation/SemanticVersioning/SemanticVersion.cs

Lines 171 to 173 in 3297736

	Major = int.Parse(parsed.Groups["Major"].Value),
	Minor = parsed.Groups["Minor"].Success ? int.Parse(parsed.Groups["Minor"].Value) : 0,
	Patch = parsed.Groups["Patch"].Success ? int.Parse(parsed.Groups["Patch"].Value) : 0,

GitVersion/src/GitVersion.Core/VersionCalculation/SemanticVersioning/SemanticVersionBuildMetaData.cs

Line 127 in 3297736

semanticVersionBuildMetaData.CommitsSinceTag = int.Parse(parsed.Groups["BuildNumber"].Value);

GitVersion/src/GitVersion.Core/VersionCalculation/SemanticVersioning/SemanticVersionPreReleaseTag.cs

Line 79 in 3297736

var number = match.Groups["number"].Success ? int.Parse(match.Groups["number"].Value) : (int?)null;

How Has This Been Tested?

I've added test cases that failed before the code changes were implemented.

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[arturcic]

@asbjornu is this a breaking change?

[asbjornu]

@asbjornu is this a breaking change?

I shouldn't think so, except perhaps if someone consumes GitVersion.Core.dll as a library. But we decided years ago that such use was unsupported and would not affect SemVer concerns.

[arturcic]

Please rebase and we can merge then

[mergify]

Thank you @asbjornu for your contribution!