Question

Your team maintains a shared .NET class library published as a NuGet package to Azure Artifacts. You want each merge to the main branch to publish a new stable package, while pull request builds publish a pre-release package that testers can install without affecting the stable version stream. You use GitHub Actions with a workflow that packs and pushes the package. Which versioning approach correctly satisfies both requirements while remaining compliant with SemVer ordering rules?

Accepted Answer

Tag main-branch builds with a version like 2.3.0 and PR builds with a version like 2.3.0-pr.42, relying on the SemVer pre-release suffix to make PR builds sort lower than the stable release.

Answer

Publish all builds as 2.3.0 and rely on Azure Artifacts views to hide PR builds from the stable feed automatically.

Answer

Tag PR builds as 2.3.0 and main-branch builds as 2.3.0-release so the release suffix marks the stable version.

Answer

Append the build number as build metadata, publishing PR builds as 2.3.0+pr.42 and main builds as 2.3.0, since build metadata differentiates the two streams.