Shoryuken Has a New Maintainer, and v7.0.0 Is Almost There

After a decade under Pablo Cantero’s stewardship, Shoryuken has a new maintainer – me. I’m grateful for his graceful handoff of this Ruby SQS library, and I’m picking up where he left off: v7.0.0.rc1 is out now, with the stable release close behind.

What’s in v7.0.0

This release modernizes the codebase substantially. It brings several improvements including:

• Rails 8.1+ features:

  • ActiveJob Continuations let jobs checkpoint progress during shutdown and resume after restart.
  • Bulk enqueuing via enqueue_all now uses SQS batch API.
  • CurrentAttributes automatically flow from enqueue to execution.

• Dependency reduction:

  • myumura removed concurrent-ruby entirely, replacing it with pure Ruby thread-safe primitives.
  • Core class monkey-patching is gone – HashUtils.deep_symbolize_keys and StringUtils.constantize replace extensions on Hash and String.
  • The gem now uses Zeitwerk for autoloading.

• Infrastructure:

  • Trusted publishing for gem releases.
  • LocalStack-based integration tests.
  • 100% YARD documentation coverage, Ruby 4.0 in CI.

Breaking Changes

• Ruby 3.2+ required (3.1 hit EOL in March 2025)
• Rails 7.2+ required (7.0 and 7.1 hit EOL in April 2025)
• aws-sdk-sqs >= 1.66 required

Stay on Shoryuken 6.x if you’re on older Ruby/Rails.

What’s Next

With v7.0.0 nearly done, my next priority is the Web UI. The community has asked for a Sidekiq-style dashboard since 2017. I built Karafka’s Web UI from scratch, so I know what’s needed: real-time queue monitoring, worker visibility, dead letter queue management, historical trends.

After that: performance optimizations, better local development experience, monitoring integrations (Prometheus, StatsD, distributed tracing).

Try the RC Now

gem 'shoryuken', '7.0.0.rc1'

Test it in staging and report issues. The sooner we find edge cases, the better the stable release.

Get Involved

The previous Slack workspace was lost, so we’re rebuilding the community. Join the new Slack to share how you’re using Shoryuken in production, what pain points you’ve hit, and what features you need. Your feedback shapes what gets built next.

Shoryuken has 23+ million downloads and serves as the primary SQS option for Ruby teams who don’t want Redis dependencies. I’m committed to keeping it healthy for years to come.

The post Shoryuken Has a New Maintainer, and v7.0.0 Is Almost There appeared first on Closer to Code.