Closed mjerem34 closed 2 years ago
Yes, sidekiq poke in the internals, it would have been fixed with https://github.com/mperham/sidekiq/pull/5489, but Mike prefered to lock redis down: https://github.com/mperham/sidekiq/commit/d566154107e6543ccb42e0d2e7eddfb529f0933e
However I thought this change was released already, but apparently it wasn't.
I'm tempted to add that method back as a noop.
Ok, I added it back in 5.0.1.
Hello, my build failed due to update of Redis.
The build log :
I fixed build by fixing Redis to 4.8.0.