Alexandre Schmitt

It looks like [deprecation warnings are still happening in CI](https://github.com/resque/resque-scheduler/runs/5711844338?check_suite_focus=true) on the latest `master` (though not related to this gem, those warnings are coming from dependencies - see https://github.com/resque/redis-namespace/issues/193 /...

@ylecuyer bumping this for consideration when you have a moment 🙏

Looks like it may still be on hold -> https://github.com/getsentry/sentry-ruby/issues/2045

@iloveitaly hi there (I came across this after finding https://github.com/resque/resque-scheduler/issues/679) I've got a scheduled job that needs to behave differently (not enqueue as configured, but kick off a separate class...

@PatrickTulskie (seeing as this PR is quite out of date, wanted to get it back on the radar for consideration) 🙏

Thanks @PatrickTulskie - I've rebased these changes and opened https://github.com/resque/resque-scheduler/pull/792, failing builds there appear unrelated to the changes (and the same as seen on `master`), but let me know if...

@PatrickTulskie thanks for looking into it, I've taken a swing at addressing the CI failures in a couple PRs (https://github.com/resque/resque-scheduler/pull/793, https://github.com/resque/resque-scheduler/pull/794) - [here's a green CI](https://github.com/codealchemy/resque-scheduler/actions/runs/11597767034/job/32292053388) with the three changes...

@PatrickTulskie please let me know if there's anything else I can do to help this along 🙇