[FSSDK-12875] trusted publishing#418
Merged
junaed-optimizely merged 1 commit intoJul 9, 2026
Merged
Conversation
junaed-optimizely
deleted the
junaed/fssdk-12875-trusted-publishing-enablement
branch
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.
Summary
This pull request updates the NuGet package publishing workflow in
.github/workflows/csharp_release.ymlto improve security and authentication practices. The main changes involve setting explicit permissions and switching to a more secure login step for publishing to NuGet.Security and authentication improvements:
id-token: writepermission to the publish job to enable secure authentication with NuGet.NuGet/login@v1step to perform NuGet authentication using credentials from GitHub secrets, replacing direct use of the API key.dotnet nuget pushcommand to use the API key output from the NuGet login step, rather than referencing the secret directly.Test plan
Existing test should pass
Issues