feat: add duplicate() method to RedisSentinel

[claygeo]

Problem

RedisClientType and RedisClusterType both expose a duplicate() method for creating a new connection with the same configuration (plus optional overrides). RedisSentinelType is missing this method, forcing users to manually reconstruct the full sentinel configuration when they need a second connection.

Common use case: pub/sub requires a dedicated connection, so users need to duplicate their sentinel connection:

const sentinel = createSentinel({ ... }).on('error', console.error);
await sentinel.connect();

// Currently impossible:
const subscriber = sentinel.duplicate();

// Users must manually reconstruct:
const subscriber = createSentinel({ ...sameConfigAgain }).on('error', console.error);

Solution

Add duplicate() to the RedisSentinel class following the exact same pattern used by RedisClient (client/index.ts:1028) and RedisCluster (cluster/index.ts):

duplicate<...>(overrides?) {
  return new (Object.getPrototypeOf(this).constructor)({
    ...this._self.#options,
    commandOptions: this._commandOptions,
    ...overrides
  }) as RedisSentinelType<...>;
}

The duplicated instance is not connected. Users call .connect() on it, same as with RedisClient.duplicate().

Changes

• packages/client/lib/sentinel/index.ts -- Added duplicate() method to RedisSentinel class

Backwards Compatibility

Additive only. No existing methods or types are changed.

Closes #3107

---

Note

Low Risk
Low risk additive change that mirrors existing duplicate() implementations on RedisClient/RedisCluster and does not alter connection or command execution paths.

Overview
Adds RedisSentinel.duplicate() to instantiate a new sentinel client using the current instance’s stored #options and #commandOptions, with optional overrides, matching the duplicate() behavior already available on RedisClient and RedisCluster.

^{Written by Cursor Bugbot for commit 1135895. This will update automatically on new commits. Configure here.}

[jit-ci]

Hi, I’m Jit, a friendly security platform designed to help developers build secure applications from day zero with an MVS (Minimal viable security) mindset.

In case there are security findings, they will be communicated to you as a comment inside the PR.

Hope you’ll enjoy using Jit.

Questions? Comments? Want to learn more? Get in touch with us.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

[nkaradzhov]

@claygeo thanks, i will have a look

[nkaradzhov]

@claygeo hi again, sorry for the delay!

Common use case: pub/sub requires a dedicated connection, so users need to duplicate their sentinel connection

That is not true. Sentinel supports pubsub out of the box. It creates and maintains a new background connection via the PubSubProxy class that is specifically dedicated for pubsub.

I do agree that we should add the method for consistency though.