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_required in the gemspec set to true as while the docs don't seem to explicitly say that doesn't apply to OIDC-based publishing, the rubygems-await codebase (which is using this workflow) does also have it enabled so I'm assuming its fine
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