Skip to content

Explain registering the signing certificate on nuget.org #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
virzak merged 1 commit into from
Sep 14, 2026
Merged

Explain registering the signing certificate on nuget.org #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,8 @@ The packages land in `artifacts/package/release`. The tests compile the core fro

CI (`.github/workflows/build.yml`) builds and tests on Ubuntu and Windows, packs, and builds the consumers. Running the workflow by hand on `master` signs the packages, pushes them to nuget.org and publishes a GitHub release.

nuget.org rejects a signed package unless the certificate it was signed with is registered on the account (Account settings > Certificates), and a version it rejects cannot be pushed again: the fix is to register the certificate and publish the next version. Trusted Signing issues a new certificate every few days, so each new one has to be registered before the first release signed with it. The certificate is in the `.signature.p7s` inside each signed package, which the `packages-signed` artifact of the run holds.

## Conventions

- Default branch `master`; topic branches and PRs for anything reviewable.
Expand Down
Loading