Add channel for Rubocop 1.24.1 #308

Activity

1. codeclimate-hermes

   assigned

   f-moya

   on Jan 3, 2022
2. BrianHawley commented on Jan 4, 2022

   

   BrianHawley

   on Jan 4, 2022

   Last edited by BrianHawley

   More actions

   You can base it on channel/beta after #309 is merged (update: it's merged).

   You can use the "beta" channel to keep up to date with the latest rubocop.
3. dgholz commented on Jan 7, 2022

   

   dgholz

   on Jan 7, 2022

   Last edited by dgholz

   Author

   More actions

   You can use the "beta" channel to keep up to date with the latest rubocop.

   Thanks @BrianHawley but we want Code Climate to run the same version of Rubocop as we have in our project's Gemfile on the latest commit on the master branch, so that devs working locally can run the same version & see the same Rubocop reports as they see in Code Climate. If Code Climate updates to a newer version of Rubocop before we can bump it in our Gemfile, then they might see a difference & spend time raising internal tickets or investigating it themselves.

   I'd much prefer it if we could bump the version in our Gemfile and our .codeclimate.yml to keep them in sync, in a single commit.

   Since your change in #309 is merged, are there any blockers you know of to creating the channel?
4. BrianHawley commented on Jan 18, 2022

   

   BrianHawley

   on Jan 18, 2022

   Last edited by BrianHawley

   More actions

   @dgholz I can't create channels, so that's one. There's also a rubocop-rails bug fix release that the PR didn't include, though that only affects fixing rather than checking, which would require another PR. Another is that 1.25.0 is out today, so I'm going to make a new PR to update beta (#310), which will also include that rubocop-rails update.

   In general though, creating new channels currently requires updates to the codeclimate CLI tool, while updating the beta channel doesn't require CLI updates. It would be possible, with a lot of work, to refactor the codeclimate tools so they don't need updates to support new rubocop channels. However, noone (not even me) has allocated the time to do that work. I have been using the beta channel to keep up, until that changes.
5. dgholz commented on Jan 31, 2022

   

   dgholz

   on Jan 31, 2022

   Author

   More actions

   @BrianHawley thanks, could you get someone who can create channels to unblock your PR? I see that Rubocop have released 1.25.0 and I'd be quite excited to let our devs know that the version of Rubocop they install locally from the Gemfile will match the version run on Code Climate. If I'd switched to the beta channel, we'd have had a mismatch until I found out about 1.25.0 & bumped it myself.
6. alauper commented on Mar 24, 2022

   

   alauper

   on Mar 24, 2022

   More actions

   @BrianHawley You can base it on channel/beta after https://github.com/codeclimate/codeclimate-rubocop/pull/309 is merged (update: it's merged).

   Is there any documentation regarding the beta channel. I'm a little confused on how it works. If I set my rubocop to version to 1.26.0 and code climate updates the beta to 1.26.1, which rubocop version will code climate test our repo with?

   https://docs.codeclimate.com/docs/rubocop#using-rubocops-newer-versions

   

   Clicking the available channels link takes you here, and lists 1.23.0 up top, which rubocop released almost 5 months ago.