Question

Your team publishes an internal .NET library to an Azure Artifacts feed. Leadership requires that every package version encode the release date so consumers can immediately identify the age of a dependency, and the versioning scheme must not require manual increment of a major/minor number for each release. The library is released on an unpredictable cadence, sometimes multiple times per day. Which versioning approach should you implement in the Azure Pipelines build that produces the NuGet package?

Accepted Answer

Use CalVer with a version format such as YYYY.MM.DD.rev, generating the revision from a pipeline counter expression so multiple same-day builds remain unique.

Answer

Use strict SemVer (MAJOR.MINOR.PATCH) and manually bump the PATCH number in the .csproj before each release.

Answer

Publish every build with the fixed version 1.0.0 and rely on the Azure Artifacts feed view (@Local, @Prerelease, @Release) to distinguish releases.

Answer

Append the Git commit SHA as the entire package version so each build is uniquely identifiable.