Support Semantic Versioning

[AdmiringWorm]

Please add support for semantic versioning.

I understand this would require some rewrite to compare (alpha,beta,rc etc...)

This woul be a great help in automatically building packages which hasn't received stable state yet,
especially on packages where the stable version is broken while the pre-release isn't.

[majkinetor]

Could you clarify it a bit by providing a concrete example ?

Package version follows the vendor version, the only thing AU does now is choco fix notation when update is forced.

[AdmiringWorm]

What I mean is support versioning like 1.10.20606.1-rc2.
If I were to try execute au using this version.
It would just fail because of the regex used to parse versions, and because it isn't supported by System.Version of course.

[majkinetor]

I didn't think this is actually supported by chocolatey.

If it is supported by choco it should be supported by AU. I set this to lower priority tho (it doesn't seem many packages use this?). If this is a problem for you, please feel free to PR.

Thanks for report.

[majkinetor]

Reference: https://docs.nuget.org/create/versioning

[AdmiringWorm]

it is supported by choco see https://chocolatey.org/packages/NuGet.CommandLine/3.4.4-rtm-final which uses the -rtm-final suffix, it is true that there isn't many packages that use this.
But that could also be because there wasn't much support for it in Chocolatey Automatic Package Updater (which I believe most still use) until quite recently.

Also the reference document on nuget you linked to have a section for semver versioning:
https://docs.nuget.org/create/versioning#user-content-really-brief-introduction-to-semver.

At the moment it isn't that much of a problem for me.
I only maintain one package which releases rc builds so I can manage with manually doing those.
Just thought it would be a nice addition.

I don't have a firm understanding of PowerShell yet, so a PR from me in the near future is unlikely.

[majkinetor]

Implemented. You can get the 7z artifact of the latest build to test it out before release if you want.

Example tests:

https://github.com/majkinetor/au/blob/master/tests/Update-Package.Tests.ps1#L110-L128

[majkinetor]

Link: https://ci.appveyor.com/api/buildjobs/8g93jmygh1dh24e1/artifacts/_build%2F2016.9.16.191542%2FAU_2016.9.16.191542.7z

[AdmiringWorm]

Thanks alot for implementing this, I'll check it out. Just got to figure out why the Push-Package function is never called in my script first.

[AdmiringWorm]

So I finally had a chance to take a look at this, and so far it seems to work great. Thanks again

[ferventcoder]

Sweet!

[majkinetor]

[SemanticVersion] added to PoSh 6:

Describe "SemanticVersion api tests" -Tags 'CI' {
5       Context "constructing valid versions" {
6           It "string argument constructor" {
7               $v = [SemanticVersion]::new("1.2.3-alpha")