All Versions
175
Latest Version
Avg Release Cycle
63 days
Latest Release
-
Changelog History
Page 5
Changelog History
Page 5
-
v5.1.3 Changes
April 02, 2018- ๐ Fix version comparison so Ruby 2.2.10 works. [#3808, nateberkopec]
-
v5.1.2 Changes
- โ Add link to docs in Web UI footer
- ๐ Fix crash on Ctrl-C in Windows [#3775, Bernica]
- โ Remove
freeze
calls on String constants. This is superfluous with Ruby 2.3+ andfrozen_string_literal: true
. [#3759] - ๐ Fix use of AR middleware outside of Rails [#3787]
- Sidekiq::Worker
sidekiq_retry_in
block can now return nil or 0 to use the default backoff delay [#3796, dsalahutdinov]
-
v5.1.1 Changes
- ๐ Fix Web UI incompatibility with Redis 3.x gem [#3749]
-
v5.1.0 Changes
- ๐ NEW Global death handlers - called when your job exhausts all retries and dies. Now you can take action when a job fails permanently. [#3721]
- ๐ NEW Enable ActiveRecord query cache within jobs by default [#3718, sobrinho] This will prevent duplicate SELECTS; cache is cleared upon any UPDATE/INSERT/DELETE. See the issue for how to bypass the cache or disable it completely.
- โฑ Scheduler timing is now more accurate, 15 -> 5 seconds [#3734]
- Exceptions during the :startup event will now kill the process [#3717]
- ๐ Make
Sidekiq::Client.via
reentrant [#3715] - ๐ Fix use of Sidekiq logger outside of the server process [#3714]
- ๐
Tweak
constantize
to better match Rails class lookup. [#3701, caffeinated-tech]
-
v5.0.5 Changes
- โก๏ธ Update gemspec to allow newer versions of the Redis gem [#3617]
- ๐จ Refactor Worker.set so it can be memoized [#3602]
- ๐ Fix display of Redis URL in web footer, broken in 5.0.3 [#3560]
- โก๏ธ Update
Sidekiq::Job#display_args
to avoid mutation [#3621]
-
v5.0.4 Changes
- ๐ Fix "slow startup" performance regression from 5.0.2. [#3525]
- ๐ Allow users to disable ID generation since some redis providers disable the CLIENT command. [#3521]
-
v5.0.3 Changes
- ๐ Fix overriding
class_attribute
core extension from ActiveSupport with Sidekiq one [PikachuEXE, #3499] - ๐ Allow job logger to be overridden [AlfonsoUceda, #3502]
- 0๏ธโฃ Set a default Redis client identifier for debugging [#3516]
- ๐ Fix "Uninitialized constant" errors on startup with the delayed extensions [#3509]
- ๐ Fix overriding
-
v5.0.2 Changes
- ๐ fix broken release, thanks @nateberkopec
-
v5.0.1 Changes
- ๐ Fix incorrect server identity when daemonizing [jwilm, #3496]
- โช Work around error running Web UI against Redis Cluster [#3492]
- โ Remove core extensions, Sidekiq is now monkeypatch-free! [#3474]
- Reimplement Web UI's HTTP_ACCEPT_LANGUAGE parsing because the spec is utterly incomprehensible for various edge cases. [johanlunds, natematykiewicz, #3449]
- โก๏ธ Update
class_attribute
core extension to avoid warnings - Expose
job_hash_context
fromSidekiq::Logging
to support log customization
-
v5.0.0 Changes
- ๐ฅ BREAKING CHANGE Job dispatch was refactored for safer integration with
Rails 5. The Logging and RetryJobs server middleware were removed and
functionality integrated directly into Sidekiq::Processor. These aren't
commonly used public APIs so this shouldn't impact most users.
Sidekiq::Middleware::Server::RetryJobs -> Sidekiq::JobRetry Sidekiq::Middleware::Server::Logging -> Sidekiq::JobLogger
- ๐ฆ Quieting Sidekiq is now done via the TSTP signal, the USR1 signal is deprecated.
- 0๏ธโฃ The
delay
extension APIs are no longer available by default, you must opt into them. - ๐ป The Web UI is now BiDi and can render RTL languages like Arabic, Farsi and Hebrew.
- ๐ Rails 3.2 and Ruby 2.0 and 2.1 are no longer supported.
- ๐ท The
SomeWorker.set(options)
API was re-written to avoid thread-local state. [#2152] - ๐ท Sidekiq Enterprise's encrypted jobs now display "[encrypted data]" in the Web UI instead of random hex bytes.
- โฌ๏ธ Please see the [5.0 Upgrade notes](docs/5.0-Upgrade.md) for more detail.
- ๐ฅ BREAKING CHANGE Job dispatch was refactored for safer integration with
Rails 5. The Logging and RetryJobs server middleware were removed and
functionality integrated directly into Sidekiq::Processor. These aren't
commonly used public APIs so this shouldn't impact most users.