Add new versioning scheme BySemVerBuildNumber in NugetCommandV2 #21484
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.
Context
Adding new versioning scheme BySemVerBuildNumber in NuGetCommandV2 task
📌 DotNetCoreCLIV2 Work Items
Task Name
NuGetCommandV2
Description
DotNetCoreCLI@2 "pack" discards pre-release tag when using versioningScheme: 'byBuildNumber'.
In this PR we have added new versioningScheme BySemVerBuildNumber that supports full SemVer 2.0 format, including:
MAJOR.MINOR.PATCH
Optional pre-release tags (-alpha, -beta.1)
Optional build metadata (+build.123)
RelatedLinks - GitHub Issue
Risk Assessment (Low / Medium / High)
Low
Change Behind Feature Flag (Yes / No)
No
Testing Performed (Low / Medium / High)
Tested Manually - BySemVerBuildNumber
Checklist