-
-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with unreleased Sidekiq 6.3.0 #636
Comments
I'll make the necessary adjustments |
Released as v7.1.6, I'm considering back-porting it but haven't found the time yet. |
Thanks for getting this patched up, @mhenrixon. And thanks for all your work on this gem. If you have time, a backport for the 6.0.x series would be awesome! 😍 |
As sidekiq 6.3.0 hasn't been released yet I haven't given this a whirl, as soon as the release is out I will and then close the issue. If you @mhenrixon want to do so beforehand, feel free. |
@teoljungberg actually, it was added already in 6.2.2 which has been released. |
Aye you're correct @mhenrixon. We're running the new naming as of this morning and it works wonders. Thanks for the quick turn around |
Sidekiq 6.2.2 released an unofficial alias of
Sidekiq::Worker
asSidekiq::Job
, with the plan to migrate to useSidekiq::Job
going forward after 6.3.0https://github.com/mperham/sidekiq/blob/237c70fe374142509e031dbbf136d57f43dd4913/lib/sidekiq/job.rb
The old
Sidekiq::Job
that was insidesidekiq/api
has since been renamed toSidekiq::JobRecord
.The text was updated successfully, but these errors were encountered: