You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove publishing to VSTS Feed from the build pipeline.
Our daily pipeline is pushing all 3 packages (client, desktop and broker) to our internal IDDP feed. But when we release version it, the internal feed gets the release versioned NuGet, but we may not necessarily release the one we tagged as release. Just like nuget.org, internal feed can take only one copy of a given version, this blocks us from publishing the actual released version to the internal feed.
For 4.47.0 release we had 3 RCs, and the first RC was pushed to the internal feed. But we released RC3 to NuGet.org.
After MSAL 4.47.0 release, we had to release a 4.47.1 to fix this issue for our 1P customers (MS Internal). This bug needs to be handled on priority to avoid such issues in the future.
The text was updated successfully, but these errors were encountered:
remove VSTS Feed completely from the build pipeline and create a VSTS feed publish pipeline
add publish parameter to the build pipeline, set it to false as default. Override for builds that needs to be published by adding the supplying the variable during release.
Remove publishing to VSTS Feed from the build pipeline.
Our daily pipeline is pushing all 3 packages (client, desktop and broker) to our internal IDDP feed. But when we release version it, the internal feed gets the release versioned NuGet, but we may not necessarily release the one we tagged as release. Just like nuget.org, internal feed can take only one copy of a given version, this blocks us from publishing the actual released version to the internal feed.
For 4.47.0 release we had 3 RCs, and the first RC was pushed to the internal feed. But we released RC3 to NuGet.org.
After MSAL 4.47.0 release, we had to release a 4.47.1 to fix this issue for our 1P customers (MS Internal). This bug needs to be handled on priority to avoid such issues in the future.
The text was updated successfully, but these errors were encountered: