ProGet: Issue: Latest versions listed at bottom of list

[MaxCascone]

ProGet version: Version 5.3.43 (Build 4-proget53)

Hi,

We've seen twice now that the latest build package published to ProGet is showing at the bottom of the list of versions.

Additionally, the "Latest Version" shown on the feed main page does not reflect the actual latest version.

I have a feeling we are not understanding something about semantic versioning and pre-release version semantics.

We are using separate Dev and Prod feeds. Ready-To-Ship packages are manually (for now) repackaged into the Prod feed. So by design we'll never have a "stable" release version in the Dev feed. Part of me feels this is overcomplicating things, but it feels "safer" to have an Approved Packages Only feed to deploy to Production with.

Example:

• 2.1.1-PLATDEV-11647-1017 is shown at the top of the list, after 2.1.1-PLATDEV-11647-1016, 2.1.1-PLATDEV-11647-1015, etc.
  At the bottom of the list is 2.1.1-develop-2018, which is the most recent build of this package.
  On the main feed page, Latest Version: 2.1.1-PLATDEV-11647-1017 is displayed.

I just saw this post which seems to be related. I tried to repackage a existing package with a lower, 3-digit version, and it didn't work, possibly because it was just a repackage and not an upload; regardless, this doesn't feel like a valid workaround.

[Dan_Woolf]

Hi @mcascone,

So this is actually working as expected. We order by the version number itself instead of the upload date, which is why you are seeing that version on the bottom. When ordering, we order first by major, then minor, then patch. So in this case 1-PLATDEV > 1-develop, which is why 2.1.1-develop-2018 drops to the bottom.

I believe we have sent this to you before, but just in case we have not. We have created an article for
Best Practices for Versioning NuGet Packages in the Enterprise. This goes into a lot more detail on NuGet versioning.

Thanks,
Dan