📦 Update workflow with configure_trusted_publisher #280
Conversation
This file contains 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
I ran `configure_trusted_publisher` to regenerate and configure trusted publishing, and copied over most of what it created. The only significant difference is that it adds `step-security/harden-runner`. The other changes are minor: renaming the workflow file and the GitHub environment, using SHA1 checksums for the actions rather than tags, etc. `configure_trusted_publisher` originally configured the trusted publisher on rubygems.org _without_ any reference to the GitHub environment. But then I made the following PR: rubygems/configure_trusted_publisher#9, and used that to generate a new RubyGems Trusted Publisher config.
nevans
force-pushed
the
configure_trusted_publisher
branch
from
2946a66
to
80c8964
Compare
|
@shugo I think this failed for |
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.
I ran
configure_trusted_publisherto regenerate and configure trusted publishing, and copied over most of what it created. The only significant difference is that it addsstep-security/harden-runner. The other changes are minor: renaming the workflow file and the GitHub environment, using SHA1 checksums for the actions rather than tags, etc.configure_trusted_publisheroriginally configured the trusted publisher on rubygems.org without any reference to the GitHub environment. But then I made the following PR: rubygems/configure_trusted_publisher#9, and used that to generate a new RubyGems Trusted Publisher config.