Automatic gem release and tag after changing version

[ekohl]

Have you looked at:

Use Github Actions to release gems

In Voxpupuli we use this Github Action to release gems after a tag has been pushed: I like this release because it makes it very easy to release. I’m proposing to apply the same to Foreman plugins where the owner is interested. To deal with security, I’m proposing to create a new account on Rubygems (besides RubyGems.org | your community gem host) that is used only for this. Then we can opt-in. On this account we’ll create an API key and store it as a Github organization secret. Only repos th…

I assume you do since you reference theforeman/actions. It feels like this is taking it a step further to also create the tag. I’ve mentally played with the same concept, but never got around to implementing it.

In the past I’ve played around with bump2version · PyPI to automate how to bump. With that it’s actually pretty trivial. Now I must admit that these days I don’t have time to contribute to bump2version anymore and perhaps there are better solutions, but it’s nice to somehow abstract it.

One benefit of manual tags that I do like (but don’t really benefit from today) is GPG signed git tags. Another thing to consider in all of this is that we can’t use 2FA on our releases today. Tim mentioned the other day they are looking into it (on Rubygems).

@lstejska

Get plugin version

      - name: Set variables
        run: |
          VER=$(bundle exec ruby -e 'puts Hola::VERSION')
          echo "VERSION=$VER" >> $GITHUB_ENV

What we use in our translations (and is more generic):

theforeman/foreman_plugin_template/blob/6423dc56e56d2b35324c692afbc16dbd59946f79/locale/Makefile#L10

Or more minimal:

ruby -rrubygems -e 'puts Gem::Specification::load(Dir.glob("*.gemspec")[0]).version'