Versions on github here and rubygems

[rubyFeedback]

On rubygems we have this:

https://rubygems.org/gems/tk

Latest version: 0.6.0

On github here we have at:

https://github.com/ruby/tk/releases

Latest version: 0.4.0, released 4 years ago.

I guess the version at rubygems.org is the current one, given that there are regular releases.

Perhaps it may be best to release the version on github here? People may otherwise think
this is the latest, and then realise it is not. Or perhaps automatically sync this; not sure if
github provides an action for syncing automatically. Automatically syncing may be best,
though, as then people can always pick any "mirror" (github or rubygems.org in this
case here).

[jeremyevans]

Rubygems.org is the official publishing point and what almost all Ruby users would use to install ruby-tk. Even when we published a release on GitHub, it doesn't actually include the gem, so the published assets are likely unhelpful to the vast majority of users.

@hsbt I'm not sure why we publish GitHub releases for gems. Is it just so we have somewhere to put the release notes? I use a GitHub discussion for that. Assuming we do want to continue publishing on GitHub, is there some automated workflow I should be using that handles publishing to both GitHub and rubygems.org?