Repository navigation
Explain registering the signing certificate on nuget.org - #6
Merged
Merged
Conversation
nuget.org rejects a signed package whose certificate is not registered on the account, and will not take the rejected version again. 1.0.23 was lost that way, so the note says to register each new Trusted Signing certificate before the first release signed with it, and where to find the certificate. Generated with Claude Code
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.
nuget.org rejected 1.0.23 because the Trusted Signing certificate was not registered yet, and will not take that version again. This notes the step in AGENTS.md; merging it also moves master to 1.0.24.
🤖 Generated with Claude Code