-
-
Notifications
You must be signed in to change notification settings - Fork 687
Open
Description
🤔 What's the problem you've observed?
The action-publish-rubygem
action was created to
- Ensure that only trusted code handles the credentials for Ruby Gems
- Provide a reusable standardized method to publish Ruby Gems in the Cucumber org.
✨ Do you have a proposal for making it better?
With trusted publishing we no longer have to use credentials. The action can authenticate itself with Ruby through GitHub. Additionally the Rubygems org on Github provides an action for publishing.
So if for every project we:
- add a trusted publisher on RubyGems.
- Use the
rubygems/release-gem
action - Remove the ruby secrets from the Release environment.
The action can be archived.
📚 Any additional context?
~/Projects/cucumber/code-search$ grep -rl "cucumber/action-publish-rubygem"
cucumber/cucumber-expressions/.github/workflows/release-rubygem.yml
cucumber/gherkin/.github/workflows/release-rubygem.yml
cucumber/aruba/.github/workflows/release.yml
cucumber/multi_test/.github/workflows/release-ruby.yml
cucumber/html-formatter/.github/workflows/release-ruby.yml
cucumber/compatibility-kit/.github/workflows/release-ruby.yml
cucumber/ci-environment/.github/workflows/release-ruby.yml
cucumber/cucumber-ruby/.github/workflows/release.yaml
cucumber/cucumber-ruby-wire/.github/workflows/release.yaml
cucumber/messages/.github/workflows/release-rubygem.yml
cucumber/tag-expressions/.github/workflows/release-rubygem.yml
cucumber/cucumber-ruby-core/.github/workflows/release.yml
cucumber/cucumber-rails/.github/workflows/release.yml
Metadata
Metadata
Assignees
Labels
No labels