Allow Rubocop versions above 1.18.x?

[emmahsax]

The requirements of this gem require rubocop ~> 1.18.0, meaning that Rubocop versions above 1.19.0 aren't allowed.

However, Rubocop doesn't support Ruby 3.2 until Rubocop version 1.26.0 Is there any reason we can't allow Rubocop 1.26 or higher?

$ bundle exec rubocop
Error: RuboCop found unknown Ruby version 3.2 in `.ruby-version`.
Supported versions: 2.5, 2.6, 2.7, 3.0, 3.1

[ashmaroli]

Hello @emmahsax,
The reason this gem locks to a certain RuboCop version is because RuboCop releases new cops every now and then, often failing CI on lines of code unrelated to tested commit / pull request.
That said, there is no reason blocking this plugin from getting itself updated to allow upto RuboCop 1.26.x, other than lack of need / motivation.

[parkr]

I think we should upgrade. There's a rubocop failure in jekyll/github-metadata#245 that is an internal error within Rubocop. Since this is locked to 1.18.x, I can't test if it's fixed in a later version.

[parkr]

The reason this gem locks to a certain RuboCop version is because RuboCop releases new cops every now and then, often failing CI on lines of code unrelated to tested commit / pull request.

Might be worthwhile changing our config to disable new cops if we're worried about this:

AllCops:
    NewCops: enable

Either way, we can stay more up-to-date if we release this more often. That's made easier now by the addition of the release workflow, so we could potentially bump our rubocop dependency, then release a new version of rubocop-jekyll and keep the dependency fixed on a single minor version. Then, dependabot-based upgrades (at least for the plugin repos) would be able to get the upgrades but handle them in a PR.

[parkr]

Fixed by #27.

[parkr]

Follow #30 for updates. Everything is ready to go, but I can't push the update. Hold tight!