Restrict Rubocop version

[pathawks]

Sometimes Rubocop will add cops in a minor version and all of a sudden CI starts breaking for reasons unrelated to any recent changes. This locks Rubocop to the current minor version so that we can start using new cops on our schedule 👍

/cc: @jekyll/core @ashmaroli

[parkr]

I don't mind that this happens, to some degree. It helps us stay current. Whenever we lock this, we end up just falling behind and it makes updates really painful because it's not just 1 or 2 cops added, it's like 38. That said, it hurts contributors who want a green CI and don't understand why it's failing.

I'll defer here.

[pathawks]

Is there any way @jekyllbot could open an issue/PR anytime this needs to be bumped? Subscribe to updates from Rubocop?

[parkr]

@pathawks That's a good idea. jekyllbot is currently stateless but I bet this would be fruitful work. We could do this for other dependencies as well by checking RubyGems against our Gemfile and gemspec.

[ashmaroli]

Is there any way @jekyllbot could open an issue/PR anytime this needs to be bumped? Subscribe to updates from Rubocop?

Love this idea..
Till date, JekyllBot needs explicit commands from the maintainers here to do something.. The only thing I found it does automatically is mark issues as stale and warn users that JekyllHelp is no longer functional..
JekyllBot opening a PR automatically would be so cool.. Hope it would also understand that we currently (as of then) do not intend to bump a dependency version..

[pathawks]

• Try to automatically clean up Rubocop violations parkr/auto-reply#9
• Submit a Pull Request when dependencies are updated parkr/auto-reply#10

[parkr]

@jekyllbot: merge +dev