Port 'Publish NuGet packages with trusted publishing' #421

Activity

1. Enkidu93

   added

   portingThis issue consists of porting code from machine to machine.py.This issue consists of porting code from machine to machine.py.

   on Nov 6, 2026
2. github-project-automation

   added this to Servalon Nov 6, 2026
3. github-project-automation

   moved this to 🆕 New in Servalon Nov 6, 2026
4. claude commented on Nov 6, 2026

   

   claudeBot

   on Nov 6, 2026 – with Claude

   Last edited by claude

   Contributor

   More actions

   Claude finished @Enkidu93's task in 12s —— View job

   ---

   Porting analysis for sillsdev/machine#622

   No code changes made, and no PR opened.

   • machine#622 only changes .github/workflows/ci.yml. It moves NuGet publishing into a separate publish job that uses NuGet trusted publishing (NuGet/login, id-token: write, a nuget environment) in place of the long-lived NUGET_API_KEY secret.
   • This is NuGet-specific, so it has no direct counterpart here. machine.py publishes to PyPI with uv publish and PYPI_API_TOKEN (.github/workflows/ci.yml:51-74).
   • A PyPI equivalent would be PyPI trusted publishing. That means id-token: write on the publish job, a GitHub environment, a trusted publisher configured on pypi.org, and dropping UV_PUBLISH_TOKEN. It is a different change from this PR and depends on settings outside the repo.
   • I can't edit files under .github/workflows, because the GitHub App doesn't have permission to.

   If you want PyPI trusted publishing, a maintainer would need to set it up with the steps above. Otherwise this issue can be closed as not applicable.
5. Enkidu93

   closed this as not plannedon Nov 10, 2026
6. github-project-automation

   moved this from 🆕 New to ✅ Done in Servalon Nov 10, 2026