ci: setup automatic publishing #57
Merged
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
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.
This sets up automatic publishing based on this guide - the workflow itself is based off this example.
For now I've decided to keep the workflow light rather than e.g. run tests or linting since this is the first time we've automated gem publishing and it's unlikely we'll actually do a lot of releases so I want to make it as easy to release a new version.
I have left
rubygems_mfa_requiredin the gemspec set totrueas while the docs don't seem to explicitly say that doesn't apply to OIDC-based publishing, therubygems-awaitcodebase (which is using this workflow) does also have it enabled so I'm assuming its fineResolves #23