Repository navigation
Publish to NuGet through trusted publishing - #40
Merged
Merged
Conversation
The publish job exchanges its OpenID Connect token for a short-lived API key with NuGet/login, using the trusted publishing policy of the nuget.org user that owns the package, so the NUGET_API_KEY secret is no longer used. A workflow_dispatch input allows publishing an existing tag on demand. Co-Authored-By: Claude Fable 5.1 <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
The publish job in
publish.ymlexchanges its OpenID Connect token for a short-lived NuGet API key withNuGet/login, through the trusted publishing policy of the nuget.org useripdatathat owns the package. TheNUGET_API_KEYsecret is no longer referenced and can be deleted. Aworkflow_dispatchinput allows publishing an existing tag on demand.How it works
id-token: write;NuGet/login@v1returnsNUGET_API_KEYas a step output, whichdotnet nuget pushuses in place of the stored key.gh workflow run publish.yml -f tag=v3.1.0publishes a tag that already exists, which the automatic release path skips.Verification
🤖 Generated with Claude Code