Repository navigation
Use trusted publishing for release publish job - #28
Merged
adamsitnik merged 1 commit intoJul 13, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the NuGet publishing flow in the reusable release workflow to use NuGet.org trusted publishing (OIDC) instead of a long-lived API key secret, aligning this repo’s release pipeline with the referenced Aspire approach.
Changes:
- Replaced the
NUGET_PACKAGE_PUSH_TOKENsecret requirement withNUGET_USERfor NuGet OIDC login. - Added
NuGet/login@v1step to obtain a short-lived NuGet API key via OIDC and used it fordotnet nuget push. - Scoped the publish job permissions to include
id-token: writefor OIDC.
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
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.
Mimic CommunityToolkit/Aspire#1453