Bump rubocop from 1.63.2 to 1.63.4
Bumps [rubocop](https://github.com/rubocop/rubocop) from 1.63.2 to 1.63.4. - [Release notes](https://github.com/rubocop/rubocop/releases) - [Changelog](https://github.com/rubocop/rubocop/blob/master/CHANGELOG.md) - [Commits](https://github.com/rubocop/rubocop/compare/v1.63.2...v1.63.4) --- updated-dependencies: - dependency-name: rubocop dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
This commit is contained in:
2
Gemfile
2
Gemfile
@@ -23,7 +23,7 @@ gem 'espeak-ruby', '~> 1.1.0' # Text-to-Voice
|
||||
gem 'rake', '~> 13.2'
|
||||
gem 'otr-activerecord', '~> 2.2.0'
|
||||
gem 'sqlite3', '~> 2.0'
|
||||
gem 'rubocop', '~> 1.63.3', require: false
|
||||
gem 'rubocop', '~> 1.63.4', require: false
|
||||
|
||||
# Geolocation support
|
||||
group :geoip do
|
||||
|
||||
10
Gemfile.lock
10
Gemfile.lock
@@ -115,7 +115,7 @@ GEM
|
||||
hashie-forbidden_attributes (~> 0.1)
|
||||
parallel (1.24.0)
|
||||
parseconfig (1.1.2)
|
||||
parser (3.3.0.5)
|
||||
parser (3.3.1.0)
|
||||
ast (~> 2.4.1)
|
||||
racc
|
||||
power_assert (2.0.3)
|
||||
@@ -166,7 +166,7 @@ GEM
|
||||
diff-lcs (>= 1.2.0, < 2.0)
|
||||
rspec-support (~> 3.13.0)
|
||||
rspec-support (3.13.0)
|
||||
rubocop (1.63.3)
|
||||
rubocop (1.63.4)
|
||||
json (~> 2.3)
|
||||
language_server-protocol (>= 3.17.0)
|
||||
parallel (~> 1.10)
|
||||
@@ -177,8 +177,8 @@ GEM
|
||||
rubocop-ast (>= 1.31.1, < 2.0)
|
||||
ruby-progressbar (~> 1.7)
|
||||
unicode-display_width (>= 2.4.0, < 3.0)
|
||||
rubocop-ast (1.31.2)
|
||||
parser (>= 3.3.0.4)
|
||||
rubocop-ast (1.31.3)
|
||||
parser (>= 3.3.1.0)
|
||||
ruby-progressbar (1.13.0)
|
||||
ruby2_keywords (0.0.5)
|
||||
rubyzip (2.3.2)
|
||||
@@ -277,7 +277,7 @@ DEPENDENCIES
|
||||
rdoc (~> 6.6)
|
||||
rest-client (~> 2.1.0)
|
||||
rspec (~> 3.13)
|
||||
rubocop (~> 1.63.3)
|
||||
rubocop (~> 1.63.4)
|
||||
rubyzip (~> 2.3)
|
||||
rushover (~> 0.3.0)
|
||||
selenium-webdriver (~> 4.20)
|
||||
|
||||
Reference in New Issue
Block a user