(GH-2679) Support release branch naming with MAJOR SemVer number only #2699
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a PR for #2679 (Support release branch naming with MAJOR SemVer number only)
Description
Modified the regex for semantic versioning and added tests for the new possible version parsing.
It is now possible to parse just the major or the major and the minor version.
Related Issue
Resolves #2679 (Support release branch naming with MAJOR SemVer number only)
Motivation and Context
It is now possible to use release branches such as release/1 or release/1.1 and GitVersion will parse 1.0.0 or 1.1.0 for it.
How Has This Been Tested?
There are two new test cases in the class SemanticVersionTests.
Checklist: