mirror of
https://framagit.org/tykayn/mastodon.git
synced 2023-08-25 08:33:12 +02:00
Bump sidekiq from 5.1.3 to 5.2.2 (#8779)
Bumps [sidekiq](https://github.com/mperham/sidekiq) from 5.1.3 to 5.2.2. - [Release notes](https://github.com/mperham/sidekiq/releases) - [Changelog](https://github.com/mperham/sidekiq/blob/master/Changes.md) - [Commits](https://github.com/mperham/sidekiq/compare/v5.1.3...v5.2.2) Signed-off-by: dependabot[bot] <support@dependabot.com>
This commit is contained in:
parent
29e2d9e1b7
commit
8096df1055
2
Gemfile
2
Gemfile
@ -74,7 +74,7 @@ gem 'mario-redis-lock', '~> 1.2', require: 'redis_lock'
|
||||
gem 'rqrcode', '~> 0.10'
|
||||
gem 'ruby-progressbar', '~> 1.4'
|
||||
gem 'sanitize', '~> 4.6'
|
||||
gem 'sidekiq', '~> 5.1'
|
||||
gem 'sidekiq', '~> 5.2'
|
||||
gem 'sidekiq-scheduler', '~> 2.2'
|
||||
gem 'sidekiq-unique-jobs', '~> 5.0'
|
||||
gem 'sidekiq-bulk', '~>0.1.1'
|
||||
|
11
Gemfile.lock
11
Gemfile.lock
@ -147,7 +147,7 @@ GEM
|
||||
coderay (1.1.2)
|
||||
colorize (0.8.1)
|
||||
concurrent-ruby (1.0.5)
|
||||
connection_pool (2.2.1)
|
||||
connection_pool (2.2.2)
|
||||
crack (0.4.3)
|
||||
safe_yaml (~> 1.0.0)
|
||||
crass (1.0.4)
|
||||
@ -419,7 +419,7 @@ GEM
|
||||
rack-attack (5.2.0)
|
||||
rack
|
||||
rack-cors (1.0.2)
|
||||
rack-protection (2.0.1)
|
||||
rack-protection (2.0.4)
|
||||
rack
|
||||
rack-proxy (0.6.4)
|
||||
rack
|
||||
@ -541,9 +541,8 @@ GEM
|
||||
scss_lint (0.57.0)
|
||||
rake (>= 0.9, < 13)
|
||||
sass (~> 3.5.5)
|
||||
sidekiq (5.1.3)
|
||||
concurrent-ruby (~> 1.0)
|
||||
connection_pool (~> 2.2, >= 2.2.0)
|
||||
sidekiq (5.2.2)
|
||||
connection_pool (~> 2.2, >= 2.2.2)
|
||||
rack-protection (>= 1.5.0)
|
||||
redis (>= 3.3.5, < 5)
|
||||
sidekiq-bulk (0.1.1)
|
||||
@ -740,7 +739,7 @@ DEPENDENCIES
|
||||
ruby-progressbar (~> 1.4)
|
||||
sanitize (~> 4.6)
|
||||
scss_lint (~> 0.57)
|
||||
sidekiq (~> 5.1)
|
||||
sidekiq (~> 5.2)
|
||||
sidekiq-bulk (~> 0.1.1)
|
||||
sidekiq-scheduler (~> 2.2)
|
||||
sidekiq-unique-jobs (~> 5.0)
|
||||
|
Loading…
Reference in New Issue
Block a user