Does ProGet support semantic versioning

We have a defined workflow where we have embraced semantic versioning everywhere and we are looking to replace our artifcate repo with something else but it looks like the packages naming just supports major.minor.patch but not full versioning of semantic versioning. Is there an option to enable this or is this on the roadmap?

Product: ProGet
Version: 4.8.4

atripp

ProGet's Universal Packages and Feeds certainly support full SemVer2.

If you're designing modern delivery processes but are still planning to shoehorn your applications into NuGet packages (i.e. meant for .NET DLLs), you really ought to consider fixing that as well. We also released Romp which extends universal packages, and gives some nice deployment options as well.

That being said, NuGet feeds and packages have whole lot of quirks (e.g. 0.01.0 != 0.1.0, etc) that make SemVer2 nearly impossible to implement without some major breaking changes. NuGet.org had a lot of problems too when the quasi-supported it in the client. So we're planning on making those changes in ProGet v5, which is scheduled for November.

We are using NuGet to deliver individual .NET DLLs of our application and separate our monolithic application into more of a module deployment so yes the shoe fits the horn. If your universal package manager can provide similar deliverables as NuGet in an application pipeline I am interested in hearing more however it would seem at this point ProGet v5 is my answer. Thanks for the quick response!

Thanks for the update; if you're packaging up DLLs for use in .NET code, then sounds like you're using the right tool for the job.

As you move towards actual microservices (i.e. separating out the application into individually-deployable components), you should definitely look into ROMP + Hedgehog.

ROMP is the packaging/automation platform (it's a free, and is basically a way to package and deploy applications).

Hedgehog is your pipeline, orchestration, approval, etc tool.

Both are coming in Beta pretty soon (but are based off of years of our automation technology and experience)

I see that version 5 is out in beta form, is there support for semantic versioning in this version? When I try to push a package with a version of 1.0.0-rc.3 I get back an error.

An error occurred processing a PUT request to http://itx-artifacts/nuget/nuget-local/: Invalid version number.

Thanks for the help!

This is only supported in "new" NuGet feeds; some of our preliminary docs are here...

https://inedo.com/support/documentation/proget/feed-types/nuget