🤔 What's the problem you're trying to solve?
The action-publish-nuget action was created to
- Ensure that only trusted code handles the credentials for NuGet
- Provide a reusable standardized method to publish Ruby Gems in the Cucumber org.
✨ What's your proposed solution?
With trusted publishing we no longer have to use credentials. The action can authenticate itself with NuGet through GitHub. Additionally the NuGet org on Github provides an action for publishing.
So if for every project we:
- Setup trusted publishing on NuGet.
- Remove the ruby secrets from the Release environment.
The action can be archived.
⛏ Have you considered any alternatives or workarounds?
mpkorstanje@nyx:~/Projects/cucumber/code-search$ grep -rl "cucumber/action-publish-nuget"
cucumber/cucumber-expressions/.github/workflows/release-nuget.yaml
cucumber/gherkin/.github/workflows/release-nuget.yaml
cucumber/html-formatter/.github/workflows/release-nuget.yaml
cucumber/messages/.github/workflows/release-nuget.yml
📚 Any additional context?
No response
🤔 What's the problem you're trying to solve?
The action-publish-nuget action was created to
✨ What's your proposed solution?
With trusted publishing we no longer have to use credentials. The action can authenticate itself with NuGet through GitHub. Additionally the NuGet org on Github provides an action for publishing.
So if for every project we:
The action can be archived.
⛏ Have you considered any alternatives or workarounds?
📚 Any additional context?
No response