Skip to content

chore: [CHA-4947] publish NuGet via Trusted Publishing - #71

Merged
itsmeadi merged 1 commit into
masterfrom
chore/CHA-4947-nuget-trusted-publishing
Aug 25, 2026
Merged

chore: [CHA-4947] publish NuGet via Trusted Publishing#71
itsmeadi merged 1 commit into
masterfrom
chore/CHA-4947-nuget-trusted-publishing

Conversation

@itsmeadi

Copy link
Copy Markdown
Collaborator

Summary

  • Switch the Release workflow from secrets.NUGET_API_KEY to nuget.org Trusted Publishing (NuGet/login@v1 + id-token: write).
  • Fail the job if OIDC login does not return a key (the old step skipped publish and looked successful).

Before merge

  1. Add repo secret NUGET_USER = nuget.org profile name (not email).
  2. Confirm the Trusted Publishing policy uses workflow file release.yml and package glob getstream-net.

After merge (to actually ship 15.3.0)

Tag v15.3.0 already exists from #70; nuget.org still has 15.2.0. Do not rerun the old failed job. Run Actions → Release → Run workflow with use_current_version = true.

Do not delete NUGET_API_KEY until that publish succeeds.

Test plan

  • NUGET_USER secret is set
  • This PR does not auto-release (chore: title)
  • After merge, manual Release with use_current_version=true publishes getstream-net 15.3.0 and creates the GitHub release

Made with Cursor

Replace the long-lived NUGET_API_KEY with GitHub OIDC (NuGet/login) so
release.yml matches nuget.org Trusted Publishing.

Co-authored-by: Cursor <cursoragent@cursor.com>
@itsmeadi
itsmeadi merged commit 5b1bc76 into master Aug 25, 2026
4 checks passed
@itsmeadi
itsmeadi deleted the chore/CHA-4947-nuget-trusted-publishing branch August 25, 2026 11:05
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