We were able to confirm that the stable builds work as expected. The commit in main that set the DotNetFinalVersionKind property to release caused the expected things to happen:
But creating isolated feeds and being in perpetual "stable" state is unnecessarily risky. We need to be able to first test packages before publishing the stable version.
So in conversation with @ViktorHofer and as suggested by @ericstj here, we will opt for keeping the branch in prerelease mode (by simply deleting the property) and when the time comes to publish a new version, we will manually trigger a job passing DotNetFinalVersionKind as an environment variable with the release value.
Note: I am testing the env var usage internally and separate to this PR.
We were able to confirm that the stable builds work as expected. The commit in
mainthat set theDotNetFinalVersionKindproperty toreleasecaused the expected things to happen:dotnet-librariesfeed stopped being used for publishing the packages. As an example, Microsoft.Bcl.HashCode still shows the rtm as the last package published (before the commit mentioned above). https://dnceng.visualstudio.com/public/_artifacts/feed/dotnet-libraries/NuGet/Microsoft.Bcl.HashCode/overview/6.0.0-rtm.24531.5But creating isolated feeds and being in perpetual "stable" state is unnecessarily risky. We need to be able to first test packages before publishing the stable version.
So in conversation with @ViktorHofer and as suggested by @ericstj here, we will opt for keeping the branch in prerelease mode (by simply deleting the property) and when the time comes to publish a new version, we will manually trigger a job passing DotNetFinalVersionKind as an environment variable with the release value.
Note: I am testing the env var usage internally and separate to this PR.