Skip to content

chore(deps): update dependency redis to v6 - #655

Open
renovate[bot] wants to merge 1 commit into
stagingfrom
renovate/redis-6.x
Open

chore(deps): update dependency redis to v6#655
renovate[bot] wants to merge 1 commit into
stagingfrom
renovate/redis-6.x

Conversation

@renovate

@renovate renovate Bot commented May 28, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
redis ^5.12.1 → ^6.2.1 age confidence

Release Notes

redis/node-redis (redis)

v6.2.1

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/redis/node-redis/compare/redis@6.2.0...redis@6.2.1

v6.2.0

Compare Source

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
⚠️ 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
🧰 Maintenance
New Contributors

Full Changelog: https://github.com/redis/node-redis/compare/redis@6.1.0...redis@6.2.0

v6.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/redis/node-redis/compare/redis@6.0.1...redis@6.1.0

v6.0.1

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/redis/node-redis/compare/redis@6.0.0...redis@6.0.1

v6.0.0

Compare Source

Changes

This is the first major release of node-redis since 5.x. The headline change is RESP3 by default, alongside broader Redis 8.8 command coverage, pubsub/cluster reliability fixes, and a bumped minimum Node.js version.

Key changes

  • RESP3 is the default protocol — opt back into RESP2 explicitly if you need the old wire format
  • Node.js 20 is the new minimum supported runtime
  • Redis 8.8 coverage — new array commands, INCREX / INCREXBYFLOAT, ZINTER/ZUNION COUNT aggregator, XNACK, CLIENT UNBLOCK
  • Sentinel & cluster pubsub fixes for failover-moved connections and sharded topology recovery
  • Stack modules exposed on pool type and the core client classes are now publicly re-exported

🔥 Breaking Changes

See the v5 → v6 migration guide for migration steps.

  • RESP3 is now the default protocol (#​3215)
  • Node.js 20 is now the minimum supported version (#​3293)
  • New default values for keepAliveInitialDelay (30s) and commandTimeout (5s) (#​3292)

🔒 Security

🚀 New Features

  • Add CLIENT UNBLOCK command (#​3266)
  • Add XNACK command with options (#​3238)
  • Add Redis 8.8 array commands (#​3285)
  • Add INCREX and INCREXBYFLOAT commands (#​3288)
  • Add COUNT aggregator to ZINTER / ZINTERSTORE / ZUNION / ZUNIONSTORE (#​3243)
  • Add FPHA option to JSON.SET (#​3235)
  • time-series: add multi-aggregation range APIs (#​3249)
  • Add duplicate() method to RedisSentinel (#​3212)
  • Parse unix:// URLs in parseURL (#​3271)
  • Expose RedisClient, RedisCluster, RedisSentinel and pool classes (#​3251)
  • Expose stack modules on the pool type (#​3267)

🐛 Bug Fixes

  • sentinel: use mapped address when failover moves pubsub connections (#​3190)
  • cluster: recover sharded pubsub topology after node reconnects (#​3223)
  • client: swallow synchronous EPIPE from writeAfterFIN (#​3283)
  • search: allow LOAD * in FT.AGGREGATE (#​3241)
  • otel: record client connection errors (#​3259)
  • entraid: bump @azure/msal-node to 5.x to drop vulnerable uuid transitive (#​3269)
  • Fix wrapper command options handling (#​3295)
  • Non-functional typo fixes (#​3244)

📚 Documentation

🧰 Maintenance

  • Add changed-file lint gate (#​3257)
  • CI: lint changed files against PR merge base (#​3265)
  • CI: build monorepo before documentation generation (#​3233)
  • Add min-release-age cooldown to .npmrc (#​3286)
  • Allow empty object types in lint config (#​3263)
  • Add hash field subkey notifications test (#​3264)
  • Restore generic-transformers spec on current APIs (#​3214)
  • Bump default docker test image through 8.8 milestones to 8.8-rc1 (#​3234, #​3236, #​3260, #​3284)
  • chore(deps): bump basic-ftp (#​3225), tmp and @inquirer/editor (#​3294)

👥 New Contributors

We'd like to thank all the contributors who worked on this release!
@​Rohan5commit, @​opensourcezeal, @​aarond-sp, @​claygeo, @​raashish1601, @​watersRand, @​PavelPashov, @​elimelt, @​nkaradzhov

Full Changelog: https://github.com/redis/node-redis/compare/redis@5.12.1...redis@6.0.0

Configuration

📅 Schedule: (in timezone Europe/Amsterdam)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label May 28, 2026
@renovate
renovate Bot force-pushed the renovate/redis-6.x branch from 75af090 to 872ffcb Compare June 24, 2026 18:00
@renovate
renovate Bot force-pushed the renovate/redis-6.x branch from 872ffcb to b052e0f Compare July 1, 2026 22:15
@renovate
renovate Bot force-pushed the renovate/redis-6.x branch from b052e0f to 92c1169 Compare July 31, 2026 21:27
@renovate
renovate Bot force-pushed the renovate/redis-6.x branch from 92c1169 to 0e6b12c Compare August 12, 2026 00:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants