Skip to content

Use trusted publishing for Ruby#326

Draft
mpkorstanje wants to merge 1 commit into
mainfrom
trusted-publishing-ruby
Draft

Use trusted publishing for Ruby#326
mpkorstanje wants to merge 1 commit into
mainfrom
trusted-publishing-ruby

Conversation

@mpkorstanje
Copy link
Copy Markdown
Member

🤔 What's changed?

The configure-rubygems-credentials actions logs in on RubyGems using
OIDC. The cucumber/action-publish-rubygem action then publishes using
those credentials.

Additionally (where applicable):

  1. Use ruby/setup-ruby with Ruby 4.0.3 to make releases
  2. Rename file to .yaml for consistency (file name matters for OIDC!)
  3. Rename action to Release RubyGems for accuracy

⚡️ What's your motivation?

Work towards closing cucumber/common#2277.

🏷️ What kind of change is this?

  • 🏦 Refactoring/debt/DX (improvement to code design, tooling, etc. without changing behaviour)

📋 Checklist:

  • Remove RUBYGEMS_API_KEY from secrets
  • Remove API Key configuration from Rubygems
  • Configure trusted publisher in Rubygems
  • I agree to respect and uphold the Cucumber Community Code of Conduct

The `configure-rubygems-credentials` actions logs in on RubyGems using
OIDC. The `cucumber/action-publish-rubygem` action then publishes using
those credentials.

Additionally:

1. Use `ruby/setup-ruby` with Ruby 4.0.3 to make releases
2. Rename file to `.yaml` for consistency (file name matters for OIDC!)
3. Rename action to Release RubyGems for accuracy
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