Summary
The release workflow packs and publishes the main .nupkg but does not produce or publish a .snupkg symbol package. Library consumers who reference CodeIndex from another .NET project cannot step into our code with a debugger.
Where
.github/workflows/release.yml:370-380 (pack step)src/CodeIndex/CodeIndex.csproj (no <IncludeSymbols> / <SymbolPackageFormat>snupkg</SymbolPackageFormat>)
Why it matters
Symbol packages are standard for any non-trivial NuGet release. Without them, debugging into CodeIndex from a downstream consumer is impossible without rebuilding from source.
Suggested approach
Add <IncludeSymbols>true</IncludeSymbols> and <SymbolPackageFormat>snupkg</SymbolPackageFormat> to CodeIndex.csproj, then update the release workflow to push both .nupkg and .snupkg to the registry. Verify symbols resolve via Source Link (depends on the deterministic-build issue).
Summary
The release workflow packs and publishes the main
.nupkgbut does not produce or publish a.snupkgsymbol package. Library consumers who reference CodeIndex from another .NET project cannot step into our code with a debugger.Where
.github/workflows/release.yml:370-380(pack step)src/CodeIndex/CodeIndex.csproj(no<IncludeSymbols>/<SymbolPackageFormat>snupkg</SymbolPackageFormat>)Why it matters
Symbol packages are standard for any non-trivial NuGet release. Without them, debugging into CodeIndex from a downstream consumer is impossible without rebuilding from source.
Suggested approach
Add
<IncludeSymbols>true</IncludeSymbols>and<SymbolPackageFormat>snupkg</SymbolPackageFormat>toCodeIndex.csproj, then update the release workflow to push both.nupkgand.snupkgto the registry. Verify symbols resolve via Source Link (depends on the deterministic-build issue).