quality.gemspec in quality-37.1.1 vs quality.gemspec in quality-38.0.0

@@ -40,26 +40,21 @@
   # per version advice here - locks quality gem version with rubocop
   # version to avoid unexplained metric-changing surprises:
   #
   # https://github.com/bbatsov/rubocop#installation
   s.add_runtime_dependency('mdl')
-  s.add_runtime_dependency('rubocop', '~> 0.78.0')
+  s.add_runtime_dependency('rubocop', '~> 0.92.0')
   # 0.2.0 had a fatal bug
   s.add_runtime_dependency('bigfiles', ['>= 0.1', '!= 0.2.0'])
   s.add_runtime_dependency('brakeman')
   s.add_runtime_dependency('high_water_mark')
   s.add_runtime_dependency('punchlist', ['>= 1.1'])
   s.add_runtime_dependency('rails_best_practices')
   s.add_runtime_dependency('rubocop-minitest')
   s.add_runtime_dependency('rubocop-rake')
   # 1.19.0 was a RuboCop 0.51.0 compatibility release
+  s.add_runtime_dependency('faraday', ['~>1'])
   s.add_runtime_dependency('rubocop-rspec', ['>=1.19.0'])
-  # not directly required - this is to workaround this issue:
-  #  https://github.com/octokit/octokit.rb/issues/1177
-  #
-  # This causes:
-  #  "uninitialized constant Faraday::Error::ClientError (NameError)"
-  s.add_runtime_dependency('faraday', ['<1'])
 
   # need above 3.2.2 to support Ruby 2.0 syntax
   #
   # 3.6.6 was a buggy release, see seattlerb/ruby_parser#183
   s.add_runtime_dependency('ruby_parser', ['>= 3.2.2', '!= 3.6.6'])