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
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
@Piedone I'm publishing the major releases for OSOCE now. I've removed all these CompatibilitySuppressions.xml files from everywhere, but for some reason in Lombiq.Privacy I got this error:
error : API compatibility errors between 'lib/net8.0/Lombiq.Privacy.Tests.UI.dll' (/home/runner/.nuget/packages/lombiq.privacy.tests.ui/9.0.0/lombiq.privacy.tests.ui.9.0.0.nupkg) and 'lib/net8.0/Lombiq.Privacy.Tests.UI.dll' (/home/runner/work/Orchard-Privacy/Orchard-Privacy/artifacts/Lombiq.Privacy.Tests.UI.10.0.0.nupkg): [Privacy.Tests.UI.csproj]
error CP0001: Type 'Lombiq.Privacy.Tests.UI.Constants.TestUser' exists on [Baseline] lib/net8.0/Lombiq.Privacy.Tests.UI.dll but not on lib/net8.0/Lombiq.Privacy.Tests.UI.dll [Lombiq.Privacy.Tests.UI.csproj]
error : API breaking changes found. If those are intentional, the APICompat suppression file can be updated by rebuilding with '/p:ApiCompatGenerateSuppressionFile=true' [Lombiq.Privacy.Tests.UI.csproj]
I thought compatibility checks are not needed when you publish a major release. Maybe it's different because here it's missing a type instead of a method. Is this a bug?
After restoring this file, NuGet publish succeeded. So I guess now it's safe to remove this file again, right?
The reason will be displayed to describe this comment to others. Learn more.
This looks like a bug, yes, and why I created Lombiq/GitHub-Actions#350. I thought that fixed itself since then, but apparently, sometimes it trips still.
And yes, after that, you may remove the file, and actually also should, because any further push will fail package validation, telling that the suppressions are unnecessary.
c7ea07e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Piedone I'm publishing the major releases for OSOCE now. I've removed all these CompatibilitySuppressions.xml files from everywhere, but for some reason in Lombiq.Privacy I got this error:
I thought compatibility checks are not needed when you publish a major release. Maybe it's different because here it's missing a type instead of a method. Is this a bug?
After restoring this file, NuGet publish succeeded. So I guess now it's safe to remove this file again, right?
c7ea07e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a bug, yes, and why I created Lombiq/GitHub-Actions#350. I thought that fixed itself since then, but apparently, sometimes it trips still.
And yes, after that, you may remove the file, and actually also should, because any further push will fail package validation, telling that the suppressions are unnecessary.
c7ea07e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good, because I've already removed it: 5933b73
c7ea07e
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great!