Repository navigation
fix: use NuGet Trusted Publishing for releases - #2
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 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.
Summary
NUGET_API_KEYsecret requirement with NuGet Trusted Publishing viaNuGet/login@v1and GitHub OIDC inpublish.yml..nupkgand.snupkgartifacts using the short-lived key issued by NuGet.publish.ymlfrom the release workflow so the NuGet policy remains bound to its configured workflow filename.Validation
CI will build, test, pack, and validate the real package consumers. A successful PR/CI run does not itself publish packages; the current release still needs the
publish.ymlworkflow dispatched forv1.0.1after this change is merged.