Update to use NuGet trusted publishing #40
Merged
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.
.github/workflows/publish.ymlto use NuGet trusted publishingSummary
Updated the
publish.ymlworkflow to use NuGet trusted publishing following the same approach used in FsAutoComplete. The changes include:Added permissions block at the top level to enable OIDC token generation:
id-token: write- Required for NuGet trusted publishingcontents: write- Required to create releasesAdded NuGet login step that uses
NuGet/login@v1action:secrets.NUGET_USERto be configuredUpdated push step to use the API key from the login step output:
${{ secrets.NUGET_KEY }}to${{steps.login.outputs.NUGET_API_KEY}}These minimal changes enable secure, short-lived authentication with NuGet using OIDC federation, improving security by removing the need for permanent API keys.
Original prompt
Fixes #39
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.