2
Vote

Take PreRelease Version number into account

description

Hello,

First, thank you for Sidewinder. We started using it on two projects at work recently.
We love it, but I think a little addition would make it even greater.

We use the GitFlow model and SemVer to version our NuGet packages. While in development, according to https://docs.nuget.org/docs/reference/versioning we use prerelease version numbers with a build number that increments at the end. Ex:
mypackage-1.2.3-unstable0123
mypackage-1.2.3-unstable0124
mypackage-1.2.3-unstable0125
...

However, when running the updater, it does not see that there is a new version because it doesn't take into account the -unstableXXXX prerelease number. We have to user /force to download the package.

Could it be possible to have Sidewinder support prerelease version numbers in package names?

Regards,

Louis-Pierre Beaumont

comments

jimbobdog wrote Mar 18, 2014 at 3:48 PM

Hi - thanks for the feedback!

Ok, so ideally you'd want something like a /prerelease switch (and IncludePreReleases() fluent update config method) to allow Sidewinder to consider prereleases as new versions to download? Default behaviour would be to ignore prerelease package versions (like now).

Is that the functionality you're looking for?

Cheers,
James

Loupi wrote Mar 18, 2014 at 5:55 PM

Hi, thanks for the quick response.

Yes, exactly, and it would see
mypackage-1.2.3-unstable0124 as an update to
mypackage-1.2.3-unstable0123.

Cheers,
Louis