Worth doing a 1.42.1 release for this?

Worth doing a 1.42.1 release for this?

I think it would be worth it, it is kind of annoying and probably a lot of people who haven't upgraded to the typo yet.

Related - I wonder if we could have caught that issue. I know rubocop has a pretty robust linter/config-validator ... presumably there'd be some code-level "load out rules and verify no warnings present" sort of check we could add to suite...

+1 on a release to fix this. Otherwise this will print on every invocation of rubocop.

Warning: Style/SafeNavigationChainLength does not support Emabled parameter.
                                                                      
Supported parameters are:                                             
                                                                      
  - Enabled                                                                                                                                 
  - Max  

We downgraded standard to 1.41.0 on our project in the meantime.

This generates hundreds of lines of noise on my projects, which leads me to consider it a fully broken release. Noise is dangerous when I need to see real issues in my build.

Apologies for the delay in cutting a release. At least two gem owners (including myself) are currently traveling without access to a computer. Trying to get ahold of someone who can cut one

v1.42.1 is out! Sorry for missing this PR