Update shoryuken requirement from >= 4.0, <= 5.3 to >= 4.0, <= 6.2

[dependabot]

Updates the requirements on shoryuken to permit the latest version.

Changelog

Sourced from shoryuken's changelog.

[v6.1.0] - 2023-11-01

• Add GitHub Codespaces

  • #698

• Fix spec for ruby 3.0

  • #727

• Upgrade test matrix. Add Ruby 3.1, Ruby 3.2 and Rails 7

  • #739

• Fire stopped event after executor is stopped

  • #741

• Allow setup custom exception handlers for failing jobs

  • #742

• Configure dependabot to update GH Actions

  • #745

• Stop the dispatching of new messages when a SIGTERM signal has been received

  • #750

[v6.0.0] - 2022-02-18

• Breaking changes: Initialize Rails before parsing config file
  • #686
  • Previously, Shoryuken read its configuration from an optional YAML file, then allowed CLI arguments to override those, then initialized the Rails application (provided that --rails or -R was specified). This behavior meant that the config file did not have access to things like environment variables that were initialized by Rails (such as when using dotenv). With this change, Rails is initialized much earlier in the process. After Rails is initialized, the YAML configuration file is interpreted, and CLI arguments are finally interpreted last. Most applications will not need to undergo changes in order to upgrade, but the new load order could technically result in different behavior depending on the application's YAML configuration file or Rails initializers.

[v5.3.2] - 2022-01-19

• (Bugfix) Preserve queue weights when unpausing queues

  • #687

• Improve error message on startup when shoryuken has insufficient permissions to access a queue

  • #691

[v5.3.1] - 2022-01-07

• (Bugfix) Fix issue where, when using the TSTP or USR1 signals for soft shutdowns, it was possible for shoryuken to terminate without first attempting to handle all messages it fetched from SQS
  • #676

[v5.3.0] - 2021-10-31

• (Refactor) Use Forwardable within Message to avoid method boilerplate

  • #681

• Add basic health check API

  • #679

... (truncated)

Commits

• See full diff 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)