Repository navigation
Conversation
Trusted Publishing is now the only supported authentication. BREAKING CHANGE: callers must provide the NUGET_USER secret and a Trusted Publishing policy on nuget.org. NUGET_TOKEN is no longer accepted.
Contributor
Author
|
Superseded: reusable workflows cannot be used with NuGet Trusted Publishing, see the composite action PR. |
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.
Follow-up to #1097. Trusted Publishing becomes the only auth method.
NUGET_USERsecret now required,NUGET_TOKENremoved frompublish-nuget.ymlandstep-dotnet-publish-nuget.ymlNuGet/loginruns unconditionally; the API key comes solely from its outputBreaking: all callers need
NUGET_USER,id-token: writeand a nuget.org Trusted Publishing policy. Merge only after every consumer is migrated (dailydevops/defaults#698 is the first).