Use NuGet trusted publishing (OIDC) for nuget.org push - #27
Merged
Conversation
Replaces the long-lived NUGET_TOKEN secret with a short-lived API key obtained via GitHub Actions OIDC through the NuGet/login action, per https://learn.microsoft.com/en-us/nuget/nuget-org/trusted-publishing. The GitHub Packages push is unaffected and still uses GITHUB_TOKEN. Requires a NUGET_USER repo secret (nuget.org username) and a Trusted Publishing policy configured on nuget.org for this repo/workflow file. The NUGET_TOKEN secret can be removed once this is verified working. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
publish-pipeline.ymlfrom a long-livedNUGET_TOKENAPI key secret to NuGet Trusted Publishing: a short-lived API key obtained via GitHub Actions OIDC through theNuGet/login@v1action.GITHUB_TOKEN) and NuGet.org push (now OIDC-based).permissions: write-allat the workflow level already grantsid-token: write, so no extra permissions block was needed.