-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🔧🔒 Configure RubyGems Trusted Publishing #265
Conversation
@hsbt Have any other bundled gems configured trusted publishing yet? I've configured this to run when pushing a specific tag pattern, but perhaps it should be triggered by some other event? I want to be sure it doesn't conflict with any of your existing tools or processes. |
@nevans Nice work. We didn't use I'm +1 to use this automation to other bundled gems 👍 |
@hsbt Great. I'll test it out on the next release. |
b115db7
to
e7f32f6
Compare
@hsbt I added made a couple of minor changes to the workflow:
Looking at other gems that have configured this (and came up in my code search), I saw three basic approaches to triggering:
I personally prefer the tag-based approach. When combined with the I made the following other changes, too:
|
This requires additional configuration on the RubyGems website: * https://guides.rubygems.org/trusted-publishing/adding-a-publisher/ * https://rubygems.org/gems/net-imap/trusted_publishers Note that the RubyGems configuration must match both of the following: * the workflow filename: `release-gem.yml` * the job's environment: `RubyGems`
e7f32f6
to
521cd34
Compare
@hsbt @shugo @segiddins FYI: v0.4.11 was packaged by this. It all seemed to work correctly. |
Great, thanks! |
This requires additional configuration on the RubyGems website: