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
To allow breaking changes in major versions, something that the baseline package validator we use during NuGet publishing doesn't do (see dotnet/sdk#40907), let's not run it in such cases.
So, if New-NuGetPackage notices a major version change (e.g. from 1.2.3 to 2.0.0) then disable baseline package validation (but only that, package validation should otherwise run).
If dotnet/sdk#40907 is implemented before, then this won't be needed.
github-actionsbot
changed the title
Don't run baselines package validation during NuGet publishing for major version changes
Don't run baselines package validation during NuGet publishing for major version changes (OSOE-857)
May 15, 2024
Piedone
changed the title
Don't run baselines package validation during NuGet publishing for major version changes (OSOE-857)
Don't run baseline package validation during NuGet publishing for major version changes (OSOE-857)
May 18, 2024
To allow breaking changes in major versions, something that the baseline package validator we use during NuGet publishing doesn't do (see dotnet/sdk#40907), let's not run it in such cases.
So, if
New-NuGetPackage
notices a major version change (e.g. from 1.2.3 to 2.0.0) then disable baseline package validation (but only that, package validation should otherwise run).If dotnet/sdk#40907 is implemented before, then this won't be needed.
Jira issue
The text was updated successfully, but these errors were encountered: