Repository navigation
Publish to NuGet with Trusted Publishing instead of an API key - #103
Merged
Merged
Conversation
nuget.org now caps API keys at 30 days and the stored NUGET_API_KEY had expired, failing the release with a 403. The release job now requests a GitHub OIDC token and exchanges it through NuGet/login for a one-hour API key, which the trusted publishing policy for this repository and workflow file authorises.
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.
The last release run failed at the NuGet push with
403 - The specified API key is invalid, has expired.... TheNUGET_API_KEYsecret was set on 2025-10-07 and has expired, and nuget.org now caps new API keys at 30 days (announcement).This switches
release.ymlto Trusted Publishing:id-token: writepermission so the job can request a GitHub OIDC token.NuGet/login@v1step (userjoadan) that exchanges it for a one-hour NuGet API key, authorised by theLinq2GraphQL-owned nuget.org policy forLinq2GraphQL/Linq2GraphQL.Client+release.yml.dotnet nuget pushuses that key instead ofsecrets.NUGET_API_KEY.Once a release has published successfully, the
NUGET_API_KEYrepository secret is unused and can be deleted.