Repository navigation
Use NuGet Trusted Publishing for release push - #251
Merged
Merged
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Replaces the long-lived
NUGET_TOKENAPI key indeployReleasewith NuGet Trusted Publishing.NuGet/login@v1exchanges the GitHub OIDC token for a short-lived API key. The last release run failed because the stored key had expired.Changes:
deployReleasegetsid-token: writefor OIDC andcontents: writeforgh release create.NuGet/login@v1step reads the nuget.org profile name from theNUGET_USERsecret.dotnet nuget pushnow uses the temporary key from the login step.Setup needed before merging:
Codeuctivity, repositoryOpenXmlPowerTools, workflow filedotnet.yml.NUGET_USERthat holds the nuget.org profile name (not the email address).deployTest, which pushes to nugettest.org, still usesNUGET_TEST_TOKENand is unchanged.