This project has moved and is read-only. For the latest updates, please go here.
1
Vote

Feature Request (CreateNewNuGetPackageFromProjectAfterEachBuild): Semantic versioning

description

Hi.

Thank you for CreateNewNuGetPackageFromProjectAfterEachBuild.

I'd like to request the ability to use semantic versioning for nuget packages such that nuget packages only use major.minor.patch instead of major.minor.patch.revision, which is what the powershell scripts currently use.

For reference, also see the discussion here.

If there's a nuspec file, I would like the powershell script to (optionally) use the assembly version (but only as major.minor.patch) when (re)creating the nuget package.

Thank you.

comments

deadlydog wrote Jan 30, 2015 at 4:23 PM

Yeah, I think I agree with you on this one. I'll try to get it into the next release. Thanks for the suggestion :)

deadlydog wrote Apr 13 at 7:06 AM

I think rather than defaulting to semantic versioning, my approach will be to add a bool parameter to the Config.ps1 to force semantic versioning, and if it's true, then we would automatically drop the revision number from the version number.