No release since 1.0.49: pack fails package validation (CP0016/CP0001/CP0014…) after the Polyfill bump, so the #70 base-name ordering fix isn't on NuGet #72

What's wrong

The latest CI run on main (run 38368127925, the merge of #70 on 2026-10-13) fails in Analyze & Release at the pack step:

Release workflow failed: Pack failed for 1 project(s): Sorting (exit code 1)

The last 400 lines of the log alone contain about 200 package-validation errors. All of them are about polyfilled BCL types compiled into ktsu.Sorting.dll, and the counts in that tail are 162 × CP0016, 13 × CP0001, 12 × CP0014, 8 × CP0015, 6 × CP0002 and 4 × CP0008. For example:

error : CP0001 (Target: 'T:System.Runtime.InteropServices.SuppressGCTransitionAttribute', Left: 'lib/netstandard2.1/ktsu.Sorting.dll', Right: 'lib/net5.0/ktsu.Sorting.dll')

The errors span netstandard2.1→net5.0, net5.0→6.0, net6.0→7.0 and net7.0→8.0.

The previous run on main, on 2026-10-07 (#65), passed. Polyfill went from 11.4.3 to 11.4.5 in #69 between the two runs. The committed Sorting/CompatibilitySuppressions.xml still holds the suppressions generated against the old Polyfill output.

Why it matters

VERSION.md says 1.0.50, but the newest stable tag is v1.0.49. #70, which sorts a base name before its numbered siblings (#61, [patch]), has never shipped, so NuGet users still get the old ordering.

Suggested fix

Regenerate the suppression file against the current Polyfill and commit it:

dotnet pack Sorting -c Release -p:ApiCompatGenerateSuppressionFile=true

Acceptance criteria

• dotnet pack -c Release succeeds locally and in CI on main
• A 1.0.50 (or later) release containing Sort a base name before its numbered siblings [patch] #70 is published