Skip to content

Use NuGet Trusted Publishing for package deployment in CI workflow - #1105

Merged
gasparnagy merged 1 commit into
mainfrom
feat/nuget-trusted-publishing
Aug 6, 2026
Merged

Use NuGet Trusted Publishing for package deployment in CI workflow#1105
gasparnagy merged 1 commit into
mainfrom
feat/nuget-trusted-publishing

Conversation

@olegKoshmeliuk

@olegKoshmeliuk olegKoshmeliuk commented Aug 6, 2026

Copy link
Copy Markdown
Member

🤔 What's changed?

Replace the static NUGET_PUBLISH_KEY secret with a short-lived API key obtained via the NuGet/login action.

⚡️ What's your motivation?

https://devblogs.microsoft.com/dotnet/strengthening-nuget-supply-chain-security-reducing-api-key-lifetime/

🏷️ What kind of change is this?

  • ⚡ New CI feature (non-breaking change which adds new behaviour)

📋 Checklist:

- [ ] I've changed the behaviour of the code
- [ ] I have added/updated tests to cover my changes.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] Users should know about my change
- [ ] I have added an entry to the "[vNext]" section of the CHANGELOG, linking to this pull request & included my GitHub handle to the release contributors list.


This text was originally taken from the template of the Cucumber project, then edited by hand. You can modify the template here.

Replace the static NUGET_PUBLISH_KEY secret with a short-lived API key
obtained via the NuGet/login action.

@gasparnagy gasparnagy left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thx!

@gasparnagy
gasparnagy merged commit b69b530 into main Aug 6, 2026
8 checks passed
@olegKoshmeliuk
olegKoshmeliuk deleted the feat/nuget-trusted-publishing branch August 6, 2026 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants