Use NuGet trusted publishing and include package README - #3
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.
Replace the expired long-lived NuGet API key with trusted publishing using NuGet/login@v1 and the pedramr NuGet account. Grant the publish job contents:read and id-token:write, then exchange the GitHub identity token immediately before pushing.
Include the repository README.md in the NuGet package and set PackageReadmeFile so NuGet renders it.
Validation: Release package creation passed; inspected the nupkg to verify README.md and the nuspec readme entry. Activation requires the matching cloudtoid NuGet trusted publishing policy for this repository and publish.yml.