Bump sidekiq from 5.1.3 to 5.2.9

[dependabot[bot]]

Bumps sidekiq from 5.1.3 to 5.2.9.

Changelog

Sourced from sidekiq's changelog.

5.2.9

• Release Rack lock due to a cascade of CVEs. #4566 Pro-tip: don't lock Rack.

5.2.8

• Lock to Rack 2.0.x to prevent future incompatibilities
• Fix invalid reference in sidekiqctl

5.2.7

• Fix stale enqueued_at when retrying #4149
• Move build to Circle CI #4120

5.2.6

• Fix edge case where a job failure during Redis outage could result in a lost job #4141
• Better handling of malformed job arguments in payload #4095
• Restore bootstap's dropdown css component [#4099, urkle]
• Display human-friendly time diff for longer queue latencies [#4111, interlinked]
• Allow Sidekiq::Worker#set to be chained

5.2.5

• Fix default usage of config/sidekiq.yml [#4077, Tensho]

5.2.4

• Add warnings for various deprecations and changes coming in Sidekiq 6.0. See the 6-0 branch. #4056
• Various improvements to the Sidekiq test suite and coverage [#4026, #4039, Tensho]

5.2.3

• Warning message on invalid REDIS_PROVIDER #3970
• Add sidekiqctl status command [#4003, dzunk]
• Update elapsed time calculatons to use monotonic clock #3999
• Fix a few issues with mobile Web UI styling [#3973, navied]
• Jobs with retry: false now go through the global death_handlers, meaning you can take action on failed ephemeral jobs. [#3980, Benjamin-Dobell]
• Fix race condition in defining Workers. [#3997, mattbooks]

... (truncated)

Commits

• 74ccba6 Fix broken test
• e2de682 Avoid redis-rb >= 4.2 due to exists API deprecation.
• e3cd1a9 bump, release
• 9031b4e Allow newer rack version due to directory traversal security bug (#4562)
• a5ada83 release
• 315d83f Fixes regression after refactoring (Closes #4456) (#4457)
• 69b8f69 bump
• 7026c8f Lock Sidekiq 5 to Rack <2.1 to avoid breaking changes, #4440
• ec3e138 Fix Rails::VERSION check for sinatra and ActiveRecord (#4433)
• c00f8e7 polish
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/hanami/contributors/network/alerts).