ci: switch NuGet publishing to Trusted Publishing (OIDC) - #6
Open
Aragas wants to merge 1 commit into
Open
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Switches NuGet publishing from the long-lived
NUGET_API_KEYsecret to Trusted Publishing: the workflow now gets a short-lived API key via GitHub OIDC usingNuGet/login@v1. The GitHub Packages push is unchanged.Before merging
Aragas) add a Trusted Publishing policy: Repository OwnerBUTR, RepositoryBUTR.CrashReport, Workflow Filepublish.ymlAfter a successful publish
NUGET_API_KEYsecret from this repo (revoke the key on nuget.org once all repos are migrated)🤖 Generated with Claude Code