support redis 5.x

[dulmandakh]

Description

support redis-py 5.x, as there is no breaking change except dropping Python 3.7 support, https://github.com/redis/redis-py/releases/tag/v5.0.0

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (add91ec) 87.44% compared to head (72dc66f) 87.44%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8504   +/-   ##
=======================================
  Coverage   87.44%   87.44%           
=======================================
  Files         148      148           
  Lines       18491    18491           
  Branches     3156     3156           
=======================================
  Hits        16169    16169           
  Misses       2033     2033           
  Partials      289      289           

Flag	Coverage Δ
unittests	87.41% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[auvipy]

we need to ensure it works with kombu well ffirst

[auvipy]

depends on celery/kombu#1790

[auvipy]

it is also passing in kombu so approving

[dulmandakh]

@auvipy could you please release a new version with the change.

[auvipy]

Not before sept 30

[Nusnus]

Not before sept 30

@auvipy if you don't have any objections I can take care of that over the weekend.

Redis 5 can be a nice upgrade indeed!

P.S
Also relevant for Kombu

[Nusnus]

Not before sept 30

@auvipy if you don't have any objections I can take care of that over the weekend.

Redis 5 can be a nice upgrade indeed!

P.S
Also relevant for Kombu

We can also finish the new patch release policy and try it out already to see if it works as expected, I'm eager to get it done so I can find time to handle the release soon if you're ok with that bro @auvipy

[auvipy]

let us first complete the release process template then we could go for it

[auvipy]

also we might need to revert another PR. Let me handle the next release first, but if i can't manage enough time, I will ping you to do so instead of me

[Nusnus]

@auvipy

let us first complete the release process template then we could go for it

See new updates on the PR.

also we might need to revert another PR. Let me handle the next release first, but if i can't manage enough time, I will ping you to do so instead of me

Sure np!
Take notes as you follow the new checklist so we can have detailed feedback and know what works/comfortable and what still requires refining. Your experience would be very valuable!