Add instructions on how to release a gem in MAINTAINING.md

[willnet]

I released a new gem myself and confirmed that bundle exec rake release works, so I added that to MAINTAINING.md.
I’m not sure what exactly should go in this TODO section, so for now I only wrote what I could.

[brendon]

Looks good. I didn't realise GitHub releases was a manual process. I assume there are ways to automate this along with the gem release task?

[brendon]

There is this as an option too: https://github.com/rubygems/release-gem

[joshbuker]

@willnet I think the todo was for stuff like how to push with MFA enabled on rubygems, and maybe switching to a CI style release pattern like @brendon suggested with the release-gem GitHub action.

Ideally, I'd like to have CI confirm that everything is set correctly (Sorcery::VERSION, primarily), then auto push the gem when creating a new release via GitHub releases.

[brendon]

Hopefully we all have MFA enabled on the rubygems side? I use the fingerprint sensor which does require following a link from the command line but it's not that bad.

[joshbuker]

Yes, I'm pretty MFA is required for all Sorcery maintainers on RubyGems. I was referring more to the step of actually passing the MFA code while pushing the gem via CLI.

[brendon]

Yes, I'm pretty MFA is required for all Sorcery maintainers on RubyGems. I was referring more to the step of actually passing the MFA code while pushing the gem via CLI.

True, I think it's probably pretty self explanatory as the CLI makes it pretty clear what it wants. At least for the key url, from memory the OTC request is a bit more terse.