Repository navigation
chore: publish to nuget.org via trusted publishing - #1120
Conversation
Short-lived OIDC credentials replace the long-lived NuGet API key secret.
There was a problem hiding this comment.
🟢 Approval recommended
The workflow correctly configures and consumes NuGet OIDC credentials in both publishing jobs.
0 open findings
What changed in this PR
Replaces long-lived NuGet API keys with short-lived OIDC credentials for package publishing.
Changes:
- Grants OIDC token permissions to publishing jobs.
- Authenticates through
NuGet/login@v1. - Uses the generated API key for NuGet pushes.
| File | Description |
|---|---|
.github/workflows/build.yml |
Migrates both package publishing jobs to trusted publishing. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
|
This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again. |
Test Results 62 files ±0 62 suites ±0 1h 21m 15s ⏱️ -53s Results for commit 15535cf. ± Comparison against base commit 70f501b. This pull request removes 62981 and adds 62981 tests. Note that renamed tests count towards both.This pull request removes 6893 skipped tests and adds 6893 skipped tests. Note that renamed tests count towards both. |
|
This is addressed in release v7.1.2. |

Short-lived OIDC credentials replace the long-lived NuGet API key secret.