Fix build version handling when creating SemanticVersion objects#3793
Conversation
The appropriate [SemanticVersion] constructor now accepts a [version] instance that has only major and minor components specified, in which case the patch component now defaults to 0.
|
@mklement0, It will cover your contributions to all Microsoft-managed open source projects. |
|
@mklement0, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request. |
|
@SteveL-MSFT Thanks; could you please also close the associated issue, #3786? |
|
Did you mean to close this? It wasn't merged, and can't be merged now because the branch was deleted. |
|
@lzybkr Sorry, my bad: I though it was already merged. |
|
@mklement0, |
|
I updated the title and description to conform to our specs. |
Fix #3786
The appropriate [SemanticVersion] constructor now accepts a [version] instance that has only major and minor components specified, in which case the patch component now defaults to 0.