Skip to content
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

Update for Sidekiq 7 #89

Merged
merged 9 commits into from
Mar 7, 2024
Merged

Conversation

martijnbolhuis
Copy link
Contributor

I took the changes from #88 and fixed the tests. Please have a look if these changes make sense.

  • Use string version of true in redis. The redis-client gem does not support
    booleans 1.
  • Replace fakeredis gem with an actual Redis in github actions because
    fakeredis is not compatible with Sidekiq 7 and the redis-client gem 2.
  • Remove unsupported Ruby version from Github actions CI.

@nglx nglx mentioned this pull request Mar 7, 2024
@nglx
Copy link
Member

nglx commented Mar 7, 2024

Thank you @martijnbolhuis & @gammons, merging it to master - please let me know if it works I'll then bump the version and release.

@nglx nglx merged commit f2ef028 into breamware:master Mar 7, 2024
6 checks passed
@gammons
Copy link
Contributor

gammons commented Mar 14, 2024

@nglx can you do a gem release with this PR in it? Thank you!

G-Rath added a commit to ackama/nzsl-share that referenced this pull request Jul 21, 2024
Support for Sidekiq v7 has been landed in the repository
(breamware/sidekiq-batch#89 &
breamware/sidekiq-batch#85), but not yet
released - hopefully that'll happen soon, but in the meantime I'm
switching us to pull from the repository because
1. it sounds like that includes some further fixes which might be useful
to us
2. the ubuntu-24 stack on Heroku no longer has `git` at runtime which
looks to be causing our deployment to fail because
`sidekiq-batch.gemspec` tries to do `git ls-remote -z` for determining
the files to include; we might still run into issues because we're
technically still using `git`, but I'm hoping this moves our usage into
the "build" phase where `git` should still be available...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants