- Fix: Allow custom polling strategy to be configured per-group via
add_group(mensfeld)add_groupnow acceptspolling_strategy:keyword argumentpolling_strategy()reads from the groups hash populated byadd_group, with fallback to raw optionsEnvironmentLoaderpassespolling_strategythrough when parsing YAML group config- #925
-
Enhancement: Add non-retryable exception middleware (Saidbek)
-
Fix: ActiveJob keyword arguments support (mensfeld)
- Jobs with keyword arguments were broken due to improper argument forwarding in
SQSSendMessageParametersSupport#initialize - Use Ruby's argument forwarding (
...) to properly pass all arguments including keyword arguments - #962
- Jobs with keyword arguments were broken due to improper argument forwarding in
-
Fix: Replace
ArgumentErrorwith customFifoDelayNotSupportedErrorfor FIFO delay errors- Provides more specific error type for programmatic error handling
- #957
See the Upgrading to 7.0 guide for detailed migration instructions.
-
Breaking: Add
Shoryuken::Errorsmodule with domain-specific error classes- Introduces
Shoryuken::Errors::BaseErroras base class for all Shoryuken errors Shoryuken::Errors::QueueNotFoundErrorfor non-existent or inaccessible SQS queuesShoryuken::Errors::InvalidConfigurationErrorfor configuration validation failuresShoryuken::Errors::InvalidWorkerRegistrationErrorfor worker registration conflictsShoryuken::Errors::InvalidPollingStrategyErrorfor invalid polling strategy configurationShoryuken::Errors::InvalidEventErrorfor invalid lifecycle event namesShoryuken::Errors::InvalidDelayErrorfor delays exceeding SQS 15-minute maximumShoryuken::Errors::InvalidArnErrorfor invalid ARN format- Replaces generic Ruby exceptions (ArgumentError, RuntimeError) with specific error types
- Introduces
-
Removed:
Shoryuken::Shutdownclass- This class was unused since the Celluloid removal in 2016
- Originally used to raise on worker threads during hard shutdown
- Current shutdown flow uses
Interruptand executor-level shutdown instead
-
Fix: Raise ArgumentError when using delay with FIFO queues
- FIFO queues do not support per-message DelaySeconds
- Previously caused confusing AWS errors with ActiveJob's
retry_on(Rails 6.1+ defaults towait: 3.seconds) - Now raises clear ArgumentError with guidance to use
wait: 0 - Fixes #924
-
Enhancement: Use fiber-local storage for logging context
- Replaces thread-local storage with Fiber[] for proper isolation in async environments
- Ensures logging context doesn't leak between fibers in the same thread
- Leverages Ruby 3.2+ fiber-local storage API
-
Enhancement: Add yard-lint with comprehensive YARD documentation
- Adds yard-lint gem for documentation linting
- Documents all public classes, modules, and methods with YARD tags
- Ensures 100% documentation coverage
-
Enhancement: Add
enqueue_allfor bulk ActiveJob enqueuing (Rails 7.1+)- Implements efficient bulk enqueuing using SQS
send_message_batchAPI - Called by
ActiveJob.perform_all_laterfor batching multiple jobs - Batches jobs in groups of 10 (SQS limit) per queue
- Groups jobs by queue name for efficient multi-queue handling
- Implements efficient bulk enqueuing using SQS
-
Enhancement: Add ActiveJob Continuations support (Rails 8.1+)
- Implements
stopping?method in ActiveJob adapters to signal graceful shutdown - Enables jobs to checkpoint progress and resume after interruption
- Handles past timestamps correctly (SQS treats negative delays as immediate delivery)
- Tracks shutdown state in Launcher via
stopping?flag - Leverages existing Shoryuken shutdown lifecycle (stop/stop! methods)
- See Rails PR #55127 for more details on ActiveJob Continuations
- Implements
-
Enhancement: Add CurrentAttributes persistence support
- Enables Rails
ActiveSupport::CurrentAttributesto flow from enqueue to job execution - Automatically serializes current attributes into job payload when enqueuing
- Restores attributes before job execution and resets them afterward
- Supports multiple CurrentAttributes classes
- Based on Sidekiq's approach using
ActiveJob::Argumentsfor serialization - Usage:
require 'shoryuken/active_job/current_attributes'andShoryuken::ActiveJob::CurrentAttributes.persist('MyApp::Current')
- Enables Rails
-
Breaking: Drop support for Ruby 3.1 (EOL March 2025)
- Minimum required Ruby version is now 3.2.0
- Supported Ruby versions: 3.2, 3.3, 3.4
- Users on Ruby 3.1 should upgrade or remain on Shoryuken 6.x
-
Breaking: Remove support for Rails versions older than 7.2
- Rails 7.0 and 7.1 have reached end-of-life (April 2025) and are no longer supported
- Supported Rails versions: 7.2, 8.0, and 8.1
- Users on older Rails versions should upgrade or remain on Shoryuken 6.x
-
Enhancement: Replace Concurrent::AtomicFixnum with pure Ruby AtomicCounter
- Removes external dependency on concurrent-ruby for atomic fixnum operations
- Introduces Shoryuken::Helpers::AtomicCounter as a thread-safe alternative using Mutex
- Reduces gem footprint while maintaining full functionality
-
Enhancement: Replace Concurrent::AtomicBoolean with pure Ruby AtomicBoolean
- Removes external dependency on concurrent-ruby for atomic boolean operations
- Introduces Shoryuken::Helpers::AtomicBoolean extending AtomicCounter
- Further reduces gem footprint while maintaining full functionality
-
Enhancement: Replace Concurrent::Hash with pure Ruby AtomicHash
-
Enhancement: Replace core class extensions with helper utilities
- Removes all core Ruby class monkey-patching (Hash and String extensions)
- Introduces Shoryuken::Helpers::HashUtils.deep_symbolize_keys for configuration processing
- Introduces Shoryuken::Helpers::StringUtils.constantize for dynamic class loading
- Eliminates unnecessary ActiveSupport dependencies
- Completely removes lib/shoryuken/core_ext.rb file
- Maintains all existing functionality while following Ruby best practices
- Improves code maintainability and reduces global namespace pollution
-
Enhancement: Implement Zeitwerk autoloading
- Replaces manual require statements with Zeitwerk-based autoloading
- Adds zeitwerk dependency for modern Ruby module loading
- Splits polling classes into properly named files (BaseStrategy, QueueConfiguration)
- Reduces startup overhead and improves code organization
- Maintains backward compatibility while modernizing the codebase
-
Enhancement: Increase
SendMessageBatchto 1MB to align with AWS -
Enhancement: Replace OpenStruct usage with Struct for inline execution
-
Enhancement: Configure server side logging (BenMorganMY)
-
Enhancement: Use -1 as thread priority
-
Enhancement: Add Support for message_attributes to InlineExecutor
-
Enhancement: Introduce trusted publishing
-
Enhancement: Add enqueue_after_transaction_commit? for Rails 7.2 compatibility
-
Enhancement: Bring Ruby 3.4 into the CI
-
Fix integration tests by updating aws-sdk-sqs and replacing moto with LocalStack
-
Breaking: Remove support of Ruby versions older than 3.1
-
Breaking: Remove support of Rails versions older than 7.0
-
Breaking: Require
aws-sdk-sqs>=1.66:
- Bugfix: Not able to use extended polling strategy (#759)
- Enable hot-reload via adding ActiveSupport::Reloader delegate (#756)
- Fix activerecord 7.1 deprecation warnings
-
Add GitHub Codespaces
-
Fix spec for ruby 3.0
-
Upgrade test matrix. Add Ruby 3.1, Ruby 3.2 and Rails 7
-
Fire stopped event after executor is stopped
-
Allow setup custom exception handlers for failing jobs
-
Configure dependabot to update GH Actions
-
Stop the dispatching of new messages when a SIGTERM signal has been received
- 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
--railsor-Rwas 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 usingdotenv). 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.
-
(Bugfix) Preserve queue weights when unpausing queues
-
Improve error message on startup when shoryuken has insufficient permissions to access a queue
- (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
-
(Refactor) Use Forwardable within Message to avoid method boilerplate
-
Add basic health check API
- Fire new
:utilization_updateevent any time a worker pool's utilization changes
- When using ActiveJob queue name prefixing, avoid applying prefix to queues configured with a URL or ARN
-
Reduce message batch sizes in
shoryuken sqs requeueandshoryuken sqs mvcommands -
Fix bug in
shoryuken sqs requeueandshoryuken sqs mvwhere those commands would exceed the SQSSendMessageBatchmaximum payload size -
Remove test stub for
Concurrent.global_io_executor -
Run integration tests on CI
- Set
executionscorrectly for ActiveJob jobs
- Fix regression in Ruby 3.0 introduced in Shoryuken 5.1.0, where enqueueing jobs with ActiveJob to workers that used keyword arguments would fail
-
Add support for specifying SQS SendMessage parameters with ActiveJob
.set -
Unpause FIFO queues on worker completion
-
Add multiple versions of Rails to test matrix
-
Migrate from Travis CI to Github Actions
- Load ShoryukenConcurrentSendAdapter when loading Rails
- Add ability to configure queue by ARN
- Add endpoint option to SQS CLI
- Add support for sending messages asynchronous with Active Job using
shoryuken_concurrent_send
- Fix Queue order is reversed if passed through CLI
- Add back attr_accessor for
stop_callback
-
Fix bug where empty queues were not paused in batch processing mode
-
Preserve batch limit when receiving messages from a FIFO queue
-
Replace static options with instance options
- Support delay per processing group
-
Fix the delegated methods to public warning
-
Specify exception class to
raise_errormatcher warning -
Fix spelling of "visibility"
- Process messages to the same message group ID one by one
- Memoization of boolean causes extra calls to SQS
-
Add support for TSTP
-
Support an empty list of queues as a CLI argument
-
Add batch support for inline workers
-
Make InlineExecutor to behave as the DefaultExecutor when calling perform_in
-
Don't force eager load for Rails 5
-
Allow Batch Size to be Specified for Requeue
-
Support FIFO queues in
shoryuken sqscommands
- Fix requeue' for FIFO queues
-
Support FIFO queues in
shoryuken sqscommands -
Allow customizing the default executor launcher
-
Exclude job_id from message deduplication when ActiveJob
-
Preserve parent worker class options
-
Add -t (shutdown timeout) option to CL
-
Support inline (Active Job like) for standard workers
- Reduce fetch log verbosity
- Auto retry (up to 3 times) fetch errors
- Make Shoryuken compatible with AWS SDK 3 and 2
-
Add support for adding a middleware to the front of chain
-
Add support for dispatch fire event
- Make Polling strategy backward compatibility
-
Allow polling strategy per group
-
Add support for creating FIFO queues
-
Allow receive message options per queue
- Fix issue with dispatch_loop and delays
- Require forwardable allowding to call
shoryukenwithoutbundle exec
- Fix stack level too deep on Ubuntu
-
Add shoryuken sqs delete command
-
Add processing groups support; Concurrency per queue support
-
Terminate Shoryuken if the fetcher crashes
- Add shoryuken sqs create command
- Allow configuring queue URLs instead of names
-
Fix miss handling empty batch fetches
-
Various minor styling changes 💄
-
Logout when batch delete returns any failure
-
Trigger events for dispatch
-
Log (warn) exponential backoff tries
-
Fix displaying of long queue names in
shoryuken sqs ls
- Fix delay option type
-
Pause endless dispatcher to avoid CPU overload
-
Auto log processor errors
-
Add a delay as a CLI param
-
Add
sqs purgecommand. See https://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_PurgeQueue.html
-
Add
sqs purgecommand. See https://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_PurgeQueue.html -
Fix "Thread exhaustion" error. This issue was most noticed when using long polling. @waynerobinson 🍻 for pairing up on this.
- Update
sqsCLI commands to useget_queue_urlwhen appropriated
- Fix custom SQS client initialization
- Fix commands sqs mv and dump
options.deletechecker
-
Replace Celluloid with Concurrent Ruby
-
Remove AWS configuration from Shoryuken. Now AWS should be configured from outside. Check this for more details
-
Remove deprecation warnings
-
Allow dynamic adding queues
-
Support retry_intervals passed in as a lambda. Auto coerce intervals into integer
-
Add SQS commands
shoryuken help sqs, such asls,mv,dumpandrequeue
-
Show a warn message when batch isn't supported
-
Require Celluloid ~> 17
-
Fix excessive logging when 0 messages found
-
Fix loading
logfilefrom shoryuken.yml -
Add support for Strict priority polling (pending documentation)
-
Add
test_workersfor end-to-end testing supporting -
Update README documenting
configure_clientandconfigure_server -
Fix memory leak caused by async tracking busy threads
-
Refactor fetcher, polling strategy and manager
- Fix aws deprecation warning message
-
Fix celluloid "running in BACKPORTED mode" warning
-
Allow setting the aws configuration in 'Shoryuken.configure_server'
-
Allow requiring a file or dir a through
-r -
Reduce info log verbosity
-
Fix auto extender when using ActiveJob
-
Add FIFO queue support
-
Deprecates initialize_aws
- Same as 2.0.10. Unfortunately 2.0.10 was removed
yankedby mistake from RubyGems.
- Fix manager #225
- Fix daemonization broken in #219
- Fix daemonization
-
Daemonize before loading environment
-
Fix initialization when using rails
-
Improve message fetching
-
Fix hard shutdown if there are some busy workers when signal received
-
Fix
rake consoletask -
Isolate
MessageVisibilityExtenderas new middleware -
Fail on non-existent queues
- Fix log initialization introduced by #191
-
Fix log initialization when using
Shoryuken::EnvironmentLoader#load
-
Add Rails 3 support
-
Allow symbol as a queue name in shoryuken_options
-
Make sure bundler is always updated on Travis CI
-
Add Rails 5 compatibility
-
Fix warnings that are triggered in some cases with the raise_error matcher
-
Add lifecycle event registration support
-
Allow passing array of messages to send_messages
-
Fix Active Job queue prefixing in Rails apps
-
Enable override the default queue with a :queue option
- Bump aws-sdk to ~> 2