Repository navigation
README: verify provenance on the release asset (nuget re-signs its copy) - #290
Merged
Merged
Conversation
…d nuget copy nuget.org re-signs every package it accepts with its repository signature, which changes the bytes — so `gh attestation verify` on the installed copy gets a 404. The attestation matches the asset attached to the GitHub release (the CI build). Correct the Installation note to say so: verify the release asset for provenance, and `dotnet nuget verify` the installed copy for the repository signature. Bump the version examples to 0.1.2. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018z5C7uNEvN24w5mSrN9sV7
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.
Verifying provenance surfaced a real doc bug. nuget.org re-signs every package it accepts with its repository certificate, which changes the bytes — so
gh attestation verifyrun on the installed (nuget.org) copy returns a 404: the attestation matches the CI-built artifact, which is the asset attached to the GitHub release, not the re-signed copy you install.Fixes the Installation note accordingly:
gh attestation verify n8PDF.0.1.2.nupkg).dotnet nuget verify).Also bumps the version examples to
0.1.2. Same correction applied to the wiki Installation page.Docs only.
🤖 Generated with Claude Code