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
{{ message }}
Repository navigation
No release since v2.0.9 (Oct 9): every main CI run since Oct 14 fails at pack on package validation (CP0014/CP0015 on Polyfill shim types) #259
Every push run of CI on main since 2026-10-14 has ended in failure or been cancelled. The last green run was f889586 (#206, Oct 9) and the last release is v2.0.9 (2026-10-09). So none of the roughly 25 fixes merged since then (#207–#239 and the Nov 4 batch) has been published.
The latest run, 41750671279 on 68f50cd (Nov 4), fails in ci / .NET / Analyze & Release while dotnet pack validates the package:
Microsoft.NET.ApiCompat.ValidatePackage.targets(39,5): error CP0015: Cannot change arguments of attribute 'System.Runtime.CompilerServices.NullableContextAttribute' on 'System.Diagnostics.CodeAnalysis.ExperimentalAttribute'. [TUI/TUI.csproj]
Microsoft.NET.ApiCompat.ValidatePackage.targets(39,5): error CP0014: Cannot remove attribute 'System.Runtime.CompilerServices.NullableContextAttribute(2)' from 'System.Diagnostics.CodeAnalysis.ExperimentalAttribute.UrlFormat.get'. [TUI/TUI.csproj]
Microsoft.NET.ApiCompat.ValidatePackage.targets(39,5): error CP0014: Cannot remove attribute 'System.Runtime.CompilerServices.NullableAttribute(0)' from 'System.Runtime.CompilerServices.DefaultInterpolatedStringHandler'. [TUI/TUI.csproj]
That run has 30 CP0014 and 3 CP0015 errors. Every one is on a type that Polyfill embeds, not on TUI's own API.
Why it matters
Consumers of ktsu.TUI are still on v2.0.9, which predates every fix merged since Oct 14 (wrap/indent, render-failure handling, Post-to-loop, emoji shortcodes and others).
A red main hides any real regression that might land behind it.
Likely cause and fix
Directory.Packages.props pins Polyfill 11.4.5. The red runs start on the same day as the Polyfill 11.4.3 → 11.4.5 bump. ScopedAction broke the same way (ktsu-dev/ScopedAction#85) and was fixed by regenerating CompatibilitySuppressions.xml for the TFMs the SDK now builds (ktsu-dev/ScopedAction#86). CredentialCache has the same failure open as ktsu-dev/CredentialCache#200.
TUI has no CompatibilitySuppressions.xml today. The suggested fix is to run dotnet pack -p:ApiCompatGenerateSuppressionFile=true on TUI/TUI.csproj, commit the generated file, and check that CI's pack step passes.
Once pack passes, the Release step will run into the org-wide expired NuGet.org key (ktsu-dev/.github#48). That is a separate problem.
Acceptance criteria
dotnet pack -c Release on main passes package validation.
Priority: High. main has been red since Oct 14, so about 25 merged fixes are unpublished. Consumers on v2.0.9 are not newly broken, so it is not Critical.
Suggested area: build/packaging. TUI has no CompatibilitySuppressions.xml yet, so this needs a new one generated, not an existing one refreshed.
Activity
matt-edmondson commentedon Nov 10, 2026
Triage
mainhas been red since Oct 14, so about 25 merged fixes are unpublished. Consumers on v2.0.9 are not newly broken, so it is not Critical.CompatibilitySuppressions.xmlyet, so this needs a new one generated, not an existing one refreshed.mainuntil this lands. Pack on pull requests so package validation fails before the merge .github#57 (pack on PRs) would prevent a repeat.dotnet pack -p:ApiCompatGenerateSuppressionFile=trueonTUI/TUI.csproj, commit the file, then confirm the CI pack step passes.Generated by Claude Code