In actions/starter-workflows#448 (comment), @chrispat said:

I don't see a reason to have two different workflows and I also expect that we will deprecate actions/setup-ruby.

I think this is a good idea.
Currently I noticed several cases where people are confused between ruby/setup-ruby and actions/setup-ruby (this action).
For instance ruby/setup-ruby#52 (comment).

As a disclaimer I'm the maintainer of ruby/setup-ruby.
I see ruby/setup-ruby as a superset of actions/setup-ruby:

• Access to essentially all Ruby versions, including alternative implementations, development builds, etc. That's 59 versions vs 3-4 for this actions/setup-ruby. Many Ruby projects or projects using Ruby want to pin to a specific teeny version.
• Automatically install an appropriate Bundler (opt-out)
• Automated caching of bundle install (opt-in)
• Maintained actively
• ruby/setup-ruby is the Ruby starter workflow

So, do you agree we should deprecate this action?
If so, how would the deprecation be implemented in practice?