Skip to content

Fix NuGet trusted publishing for release tags - #156

Merged
dfederm merged 1 commit into
mainfrom
dfederm/fix-referencetrimmer-nuget-trusted-publishing
Oct 15, 2026
Merged

dfederm merged 1 commit into
mainfrom
dfederm/fix-referencetrimmer-nuget-trusted-publishing

Conversation

@dfederm

@dfederm dfederm commented Oct 15, 2026

Copy link
Copy Markdown
Owner

Summary

The v3.5.12 release failed to publish because the workflow had OIDC permission but did not obtain an API key for dotnet nuget push. This adds NuGet/login@v1 to exchange the GitHub token for a short-lived NuGet.org key and passes that key to the push, without adding a long-lived secret.

Why this is safe

  • Login and push run only for v* tags; build, test, NuGet.org source, and --skip-duplicate behavior are unchanged.
  • The change is confined to the release workflow. No application code, GitHub Secrets, or NuGet.org policy was changed.

Validation

Check Result
actionlint v1.7.12 Passed
YAML parse and workflow structure check Passed: login immediately precedes push, both share the tag guard, and push uses the login output
git diff --check Passed

Live token exchange and package publication were not tested; they require a tag-triggered release against the configured NuGet.org trusted-publisher policy.

Copilot-Session: 07e784f1-cfc4-4c30-b264-58e82bb4b2cf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant