Use NuGet trusted publishing#4
Merged
Merged
Conversation
rtreit
marked this pull request as ready for review
July 15, 2026 22:10
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.
Replace the long-lived NuGet API key with NuGet Trusted Publishing through GitHub OIDC. The registry workflow now requests a short-lived key immediately before pushing CatHub.Protocol, uses the Node 24 NuGet login action, and documents the required policy and repository variable.\n\nValidated with actionlint. The NuGet login action manifest declares the Node 24 runtime.