node-redlock icon indicating copy to clipboard operation
node-redlock copied to clipboard

Version 5 release schedule

Open andrejleitner opened this issue 3 years ago • 14 comments
trafficstars

Is there a plan to release version 5 in the foreseeable future?

andrejleitner avatar Mar 16 '22 12:03 andrejleitner

Sorry if this is off-topic, ioredis has just released v5.0.0. I think it would be nice if this update could be added to v5 😄.

luin avatar Mar 29 '22 16:03 luin

Will the current version work with ioredis 5? The type definitions don't quite match, but they're not actually correct anyhow. They define it as:

interface CompatibleRedisClient {
    eval(args: EvalArg[], callback?: (err: Error | null, res: any) => void): any;
}

Whereas in the 4.2 codebase, the only function called on the client is evalsha

ehaynes99 avatar Aug 04 '22 17:08 ehaynes99

We want to upgrade to ioredis v5, will you update in the near future? We can help with the migration if you need anything.

wolfido92 avatar Sep 05 '22 11:09 wolfido92

Is there any update here? We have a library conflict with typeorm, which uses a newer version of io-redis, and we need to update to that.

anton-brass avatar Sep 20 '22 17:09 anton-brass

Hello guys, any news for the v5 release? Thanks

palumbamboo avatar Oct 18 '22 13:10 palumbamboo

I have opened PR to potentially get this done. https://github.com/mike-marcacci/node-redlock/pull/231

Nikamura avatar Oct 24 '22 14:10 Nikamura

@mike-marcacci Are you open to adding any maintainers of this project?

ChrisZieba avatar Mar 21 '23 17:03 ChrisZieba

Hi @ChrisZieba, I would actually be very interested in that. This project continues to work well in the places where I have it deployed, and other responsibilities have prevented me from giving it much time that isn't directly related to those use-cases. There are some finer points about redlock that I'd need a maintainer to understand – a fair number of requests have come in around use patterns that are outside the scope of this tool and would be unsound, so I wouldn't want to make changes that encourage these.

I've avoided publishing a final v5 for far too long now... I think incorporating the miscellaneous fixes and improvements (and exploring a couple reported bugs) are long overdue, but this is a can I've obviously been kicking for far too long now.

Is this something you'd be interested in, or know someone who would be capable and willing to take that on?

mike-marcacci avatar Mar 23 '23 04:03 mike-marcacci

Any news on this? :/

mze9412 avatar Jun 07 '23 08:06 mze9412

The weirdest thing is that the latest dist tag on npm points to the 5.0.0-beta.2 version (which is not even in the "releases" section on GitHub), while it should point only to a stable version, which should be 4.2.0 I guess.

Does it mean that the 5.0.0-beta.2 is actually stable? Is it safe to use it in production? Or is this just a publishing mistake?

slavafomin avatar Aug 03 '23 10:08 slavafomin

Release of 5.0.0-beta.2 was in March 2022. If it was an mistake, there was plenty of time to correct it. IMHO the Project looks like it´s dead.

develth avatar Oct 13 '23 08:10 develth

I've rewritten this in more modern infra - ioredis5, TS, and vitest. Published as @sesamecare-oss/redlock. Happy to try and make a PR if it would be welcome.

https://github.com/sesamecare/redlock

djMax avatar Oct 30 '23 00:10 djMax

I've rewritten this in more modern infra - ioredis5, TS, and vitest. Published as @sesamecare-oss/redlock. Happy to try and make a PR if it would be welcome.

https://github.com/sesamecare/redlock

I heavily support this idea!

You could just open the PR regardless, then at least the community members in this thread could look and provide some feedback.

yharaskrik avatar Oct 30 '23 02:10 yharaskrik