Setup Trusted Publishing #2405
Merged
Setup Trusted Publishing #2405
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-project-automation
bot
moved this from In progress / Pending Review
to Done
in Open Source
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close #2224
What are you trying to accomplish?
Setting up Trusted Publishing, to improve software supply chain safety.
What approach did you choose and why?
I added a Trusted Publisher on RubyGems: https://rubygems.org/gems/view_component/trusted_publishers (access to this link is limited to maintainers).
Whenever we push a new tag starting with
v, a specific workflow (push_gem) runs in Github Actions and takes care of publishing the gem to RubyGems.Anything you want to highlight for special attention from reviewers?
As advised by RubyGems, this new workflow runs in a dedicated
releaseenvironment, limited to maintainers.