Skip to content

Use NuGet Trusted Publishing for releases - #7

Merged
Benziza merged 1 commit into
mainfrom
release/trusted-publishing
Sep 17, 2026
Merged

Benziza merged 1 commit into
mainfrom
release/trusted-publishing

Conversation

@Benziza

@Benziza Benziza commented Sep 17, 2026

Copy link
Copy Markdown
Owner

Summary

  • Replace the long-lived NuGet API key with NuGet.org Trusted Publishing through GitHub OIDC.
  • Match the Benziza NuGet.org account and document the exact policy fields.

Verification

  • dotnet test WhyConfig.slnx -c Release --no-restore (10 passed)
  • dotnet pack src/WhyConfig.Cli/WhyConfig.Cli.csproj -c Release --no-restore creates the 0.1.0 tool package.
  • Publishing remains manual and will run only from main after the NuGet.org policy is created.

@Benziza
Benziza merged commit 864c857 into main Sep 17, 2026
2 checks passed
@Benziza
Benziza deleted the release/trusted-publishing branch September 17, 2026 19:40
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.

1 participant