Repository navigation
ci: publish to NuGet with Trusted Publishing - #184
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. WalkthroughThe release workflow adds tag-gated NuGet login. The package push uses the API key returned by the login action instead of the repository secret. ChangesNuGet release authentication
Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Merge Risk:
|
The NuGet API keys expired on 2026-11-01 and nuget.org now caps new keys at 30 days. This switches the release job to NuGet Trusted Publishing: the job exchanges a GitHub OIDC token for a short-lived API key via
NuGet/login, so there is no stored key to rotate.The matching Trusted Publishing policy (owner NosCore, repo NosCoreIO/NosCore.ParserInputGenerator, workflow
dotnet.yml) is already active on nuget.org.Once this is merged and a tag publishes successfully, the
NUGET_API_KEYrepo secret and the expired nuget.org key can be deleted.🤖 Generated with Claude Code
Summary by CodeRabbit