Fix: pass OIDC API key to nuget push command#92
Merged
Conversation
The NuGet/login step outputs the API key but the push command wasn't using it. Add step id and reference the output via --api-key. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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
1 participant
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.
The trusted publishing workflow merged in #91 exchanges an OIDC token for a NuGet API key via
NuGet/login@v1, but the push command wasn't actually using the resulting key. This caused a 401 "An API key must be provided" error.Fix:
id: nuget-loginto the login step so its outputs are referenceable--api-key ${{ steps.nuget-login.outputs.NUGET_API_KEY }}