chore(deps): bump the production-dependencies group with 2 updates

[dependabot]

Bumps the production-dependencies group with 2 updates: express-rate-limit and redis.

Updates express-rate-limit from 8.6.1 to 8.6.2

Release notes

Sourced from express-rate-limit's releases.

v8.6.2

You can view the changelog here.

Commits

• c416f78 8.6.2
• defb334 v8.6.2 changelog
• 7dd82cf fix: key IPv4-in-IPv6 addresses by range, not notation (#667)
• 4e23dbb chore(deps): bump ip-address from 10.3.1 to 10.4.0 (#666)
• 607ef1f chore(deps): bump ip-address from 10.2.0 to 10.3.1 (#664)
• d2370f6 chore(deps-dev): bump the development-dependencies group with 5 updates (#663)
• See full diff in compare view

Updates redis from 6.1.0 to 6.2.0

Release notes

Sourced from redis's releases.

redis@6.2.0

6.2.0

✨ Highlights

Cluster commands now follow the server's request/response policies. node-redis reads each command's routing policy from the server's COMMAND metadata and routes and aggregates accordingly, so the cluster client behaves much more like a single server. Multi-key commands that span hash slots — MGET, MSET, DEL, EXISTS, TOUCH, UNLINK — are transparently split per slot and their replies reassembled in caller order, so cross-slot calls that previously failed with CROSSSLOT now just work. Fan-out commands such as KEYS, DBSIZE, FLUSHALL, PING, WAIT, SCRIPT EXISTS and CONFIG SET run across every shard (or every node) and their replies are aggregated per the server's policy, SCAN walks the whole cluster behind a per-client virtual cursor, and RANDOMKEY / FT.CURSOR get correct cluster-aware routing. Replica read-scaling was also aligned with the server flags, so read-only keyless commands (DBSIZE, KEYS, SCAN, RANDOMKEY, and the RediSearch / time-series reads) can be served from replicas again.

⚠️ Behavior change for the raw sendCommand path: a table-recognized command sent raw — e.g. cluster.sendCommand(['DBSIZE']) — now follows its policy (fan-out and aggregate) instead of hitting a single node. Callers who relied on raw commands for per-node operations should target a specific node with cluster.nodeClient(node).sendCommand(...).

This release also brings a broad wave of new command coverage across the client and modules. The time-series package gains the most: new TS.NRANGE/TS.NREVRANGE multi-key pivot commands, a TS.READ cursor reader, TS.QUERYLABELS, EXCLUDEEMPTY on MRANGE/MREVRANGE, and multi-aggregator support. RediSearch adds FT.ALIASLIST, a COLLECT reducer for FT.AGGREGATE, HNSW RERANK, timeout warnings on the FT.SEARCH family, and the full set of stemmer languages. The core client adds SUNIONCARD/SDIFFCARD, LMOVEM/BLMOVEM, ZREVRANK WITHSCORE, COMMAND DOCS, and XREAD MAXCOUNT/MAXSIZE. A large batch of correctness fixes lands for zero-valued optional arguments (LIMIT 0, DB 0, SAMPLES 0, ENTRIESREAD 0, IDLETIME/FREQ 0, ENTRIESADDED 0) that were previously dropped from the wire, alongside several cluster and sentinel connection-lifecycle fixes.

The new HIMPORT command family (managed fieldset lifecycle) ships as experimental — see the warning below.

🚀 New Features

• feat(client): request/response policy routing for cluster commands (multi_shard split, fan-out aggregation, special SCAN/RANDOMKEY/FT.CURSOR) (#2996) — @​nkaradzhov
• feat: add COMMAND DOCS support (#3362) — @​Hashim1999164
• feat(client): add LMOVEM and BLMOVEM commands (#3340) — @​nkaradzhov
• feat(client): add SUNIONCARD and SDIFFCARD set-cardinality commands (#3336) — @​nkaradzhov
• feat(client): add zRevRankWithScore (#3279) — @​raashish1601
• feat(xread): add MAXCOUNT / MAXSIZE options (#3335) — @​nkaradzhov
• feat(search): expose timeout warnings on the FT.SEARCH family (#3338) — @​nkaradzhov
• feat(search): add missing RediSearch stemmer languages (#3350) — @​nkaradzhov
• feat(search): add FT.ALIASLIST (#3351) — @​nkaradzhov
• feat(search): add RERANK parameter for HNSW vector fields (#3356) — @​nkaradzhov
• feat(search): add COLLECT reducer to FT.AGGREGATE (#3310) — @​nkaradzhov
• feat(time-series): add TS.NRANGE / TS.NREVRANGE multi-key pivot commands (#3337) — @​nkaradzhov
• feat(time-series): support multiple aggregators per key in TS.NRANGE / TS.NREVRANGE (#3360) — @​nkaradzhov
• feat(time-series): add TS.QUERYLABELS (LABELS and VALUES forms) (#3354) — @​nkaradzhov
• feat(time-series): add EXCLUDEEMPTY to TS.MRANGE / TS.MREVRANGE (#3352) — @​nkaradzhov
• feat(time-series): add TS.READ cursor-read command (#3322) — @​nkaradzhov
• feat(json): add reviver support to GET, MGET, and ARRPOP (#3205) — @​JeanSamGirard

⚠️ Experimental

• feat(client): add HIMPORT command family with managed fieldset lifecycle (#3381) — @​nkaradzhov. The HIMPORT family and its FieldsetRegistry/PreparedFieldsets API are experimental and unstable; the surface may change or be removed in a future release. Do not depend on it in production.

🐛 Bug Fixes

• fix(cluster): reject commands before the cluster topology is ready (#3321) — @​GiHoon1123
• fix(cluster): rebind abort/timeout listeners when a command moves to another queue (#3367) — @​GiHoon1123
• fix(cluster): make extractAllCommands drain the write queue (#3364) — @​GiHoon1123
• fix(sentinel): reject connect() instead of hanging when the resolved master is unreachable (#3331) — @​GiHoon1123
• fix(client): include the acquire-timeout duration in the pool timeout error message (#3382) — @​Piyush0049
• fix(client): reject the in-flight connect attempt when the socket dies during the initiator (#3374) — @​nkaradzhov
• fix(client): correct DoublyLinkedList head removal (#3320) — @​abhijeet117
• fix(client): XADD/XTRIM with LIMIT 0 must emit the argument (#3342) — @​Develop-KIM
• fix(client): XGROUP CREATE/SETID with ENTRIESREAD 0 must emit the argument (#3333) — @​Develop-KIM
• fix(client): XSETID with ENTRIESADDED 0 must emit the argument (#3324) — @​spokodev
• fix(client): MEMORY USAGE must emit SAMPLES when 0 (#3328) — @​Develop-KIM
• fix(client): RESTORE with IDLETIME/FREQ 0 must emit the argument (#3323) — @​spokodev
• fix(client): GETEX PXAT with a Date must encode milliseconds (#3317) — @​spokodev
• fix(client): COPY with DB 0 must emit the DB argument (#3318) — @​spokodev

... (truncated)

Commits

• b48e0d3 Release redis@6.2.0
• 23b33ed Release entraid@6.2.0
• 71b820b Release time-series@6.2.0
• 2dde5df Release search@6.2.0
• 6164fd6 Release json@6.2.0
• 79521a5 Release bloom@6.2.0
• 22fbee6 Release client@6.2.0
• f2a432f Request response policies (#2996)
• 043d304 feat: add COMMAND DOCS support (#3362)
• 87623a6 fix(client): include acquire timeout duration in pool timeout error message (...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions