chore(deps): bump rq from 1.16.2 to 2.0.0

[dependabot]

Bumps rq from 1.16.2 to 2.0.0.

Release notes

Sourced from rq's releases.

v2.0

New Features

• Multiple job executions: a job can now have multiple executions running simultaneously. This will enable future support for long running scheduled jobs. Thanks @​selwin!
• Worker(default_worker_ttl=10) is deprecated in favor of Worker(worker_ttl=10). Thanks @​stv8!
• Added a cleanup parameter to registry.get_job_ids() and registry.get_job_count(). Thanks @​anton-daneyko-ultramarin!
• Added support for AWS Elasticache Serverless Redis. Thanks @​bobbywatson3!
• You can now specify TTL for deferred jobs. Thanks @​hberntsen!
• RQ's code base is now typed (mostly). Thanks @​terencehonles!
• Other minor fixes and improvements. Thanks @​hongquan, @​rbange, @​jackkinsella, @​terencehonles, @​wckao, @​sim6!

Breaking Changes

• Dropped support for Redis server < 4
• RoundRobinWorker and RandomWorker are deprecated. Use --dequeue-strategy <round-robin/random> instead.
• Job.__init__ requires both id and connection to be passed in.
• Job.exists() requires connection argument to be passed in.
• Queue.all() requires connection argument.
• @job decorator now requires connection argument.
• Built in Sentry integration has been removed. To use Sentry with RQ, please refer to Sentry's docs.

Bug Fixes

• Fixed an issue where abandoned jobs are sometimes not enqueued. Thanks @​Marishka17!
• Fixes an issue where Redis connection does not expose name attribute. Thanks @​wckao!
• job.get_status() will now always return JobStatus enum. Thanks @​indepndnt!
• Queue key should always be created even if jobs are deferred. Thanks @​sim6!
• RQ's pubsub thread will now attempt to reconnect on Redis connection errors. Thanks @​fcharlier!

Changelog

Sourced from rq's changelog.

RQ 2.0 (unreleased)

New Features:

• Multiple job executions: a job can now have multiple executions running simultaneously. This will enable future support for long running scheduled jobs. Thanks @​selwin!
• Worker(default_worker_ttl=10) is deprecated in favor of Worker(worker_ttl=10). Thanks @​stv8!
• Added a cleanup parameter to registry.get_job_ids() and registry.get_job_count(). Thanks @​anton-daneyko-ultramarin!
• Added support for AWS Elasticache Serverless Redis. Thanks @​bobbywatson3!
• You can now specify TTL for deferred jobs. Thanks @​hberntsen!
• RQ's code base is now typed (mostly). Thanks @​terencehonles!
• Other minor fixes and improvements. Thanks @​hongquan, @​rbange, @​jackkinsella, @​terencehonles, @​wckao, @​sim6!

Breaking Changes:

• Dropped support for Redis server < 4
• RoundRobinWorker and RandomWorker are deprecated. Use --dequeue-strategy <round-robin/random> instead.
• Job.__init__ requires both id and connection to be passed in.
• Job.exists() requires connection argument to be passed in.
• Queue.all() requires connection argument.
• @job decorator now requires connection argument.
• Built in Sentry integration has been removed. To use Sentry with RQ, please refer to Sentry's docs.

Bug Fixes:

• Fixed an issue where abandoned jobs are sometimes not enqueued. Thanks @​Marishka17!
• Fixes an issue where Redis connection does not expose name attribute. Thanks @​wckao!
• job.get_status() will now always return JobStatus enum. Thanks @​indepndnt!
• Queue key should always be created even if jobs are deferred. Thanks @​sim6!
• RQ's pubsub thread will now attempt to reconnect on Redis connection errors. Thanks @​fcharlier!

Commits

• 3545ff3 Bump to version 2.0
• b145f12 Prepare v2 docs (#1998)
• 899e2ec Updated changelog
• 3810cc3 Bump actions/setup-python from 5.2.0 to 5.3.0 (#2134)
• 3e2e26e Add an exception handler for the pubsub thread (#2132)
• f4283af Allow to get job count and job IDs without cleanup (#2133)
• b1620da Updated the docstring of registry.get_job_ids()
• ba5c338 Fix flaky tests
• 809a20a [AWS Elasticache Serverless Redis] Handle redis servers that return non-strin...
• fc9610a Added desc argument to registry.get_job_ids() (#2129)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)