Bump redis from 6.0.1 to 6.1.0

[dependabot]

Bumps redis from 6.0.1 to 6.1.0.

Release notes

Sourced from redis's releases.

redis@6.1.0

What's Changed

• feat: add key prefixing (fixes #2982) by @​gajus in redis/node-redis#3312
• feat(cluster): add getNodeClientForKey for WATCH/MULTI/EXEC by @​nkaradzhov in redis/node-redis#3315

New Contributors

• @​gajus made their first contribution in redis/node-redis#3312

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

Commits

• 9ba65dd Release redis@6.1.0
• d400bc9 Release entraid@6.1.0
• 27c0b71 Release time-series@6.1.0
• 5044e44 Release search@6.1.0
• 57aba53 Release json@6.1.0
• c19ba5b Release bloom@6.1.0
• 323e2bc Release client@6.1.0
• a476aa6 feat(cluster): add getNodeClientForKey for WATCH/MULTI/EXEC (#3315)
• 7ae4652 feat: add key prefixing (#3312)
• See full diff 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[diffy-bot]

Summary

Updated Redis dependency from 6.0.1 to 6.1.0 and refreshed lockfile entries. Several redis-related packages and a few tooling packages (browserslist, caniuse-lite, electron-to-chromium, node-releases, baseline-browser-mapping) were bumped in pnpm-lock.yaml.

Files changed

• apps/server/package.json — dependency bump for "redis"
• pnpm-lock.yaml — lockfile updates for redis, @redis/* packages, and multiple transitive packages/snapshots

Key changes

• apps/server/package.json

  • "redis": "^6.0.1" → "^6.1.0"

• pnpm-lock.yaml

  • Global update of redis and related packages from 6.0.1 → 6.1.0
  • Many package resolutions and snapshot entries updated to match new versions and integrity hashes
  • Tooling / data dependencies updated:
    • baseline-browser-mapping 2.10.40 → 2.10.43
    • browserslist 4.28.4 → 4.28.6
    • caniuse-lite 1.0.30001799 → 1.0.30001806
    • electron-to-chromium 1.5.380 → 1.5.393
    • node-releases 2.0.50 → 2.0.51
    • update-browserslist-db references adjusted to browserslist@4.28.6

Notable package bumps (selected)

• redis: 6.0.1 → 6.1.0
• @redis/client: 6.0.1 → 6.1.0
• @redis/bloom: 6.0.1 → 6.1.0
• @redis/json: 6.0.1 → 6.1.0
• @redis/search: 6.0.1 → 6.1.0
• @redis/time-series: 6.0.1 → 6.1.0
• baseline-browser-mapping: 2.10.40 → 2.10.43
• browserslist: 4.28.4 → 4.28.6
• caniuse-lite: 1.0.30001799 → 1.0.30001806
• electron-to-chromium: 1.5.380 → 1.5.393
• node-releases: 2.0.50 → 2.0.51

Suggestions

• Check Node engine compatibility: many @redis/* packages and redis@6.1.0 in the lockfile list engines requiring Node >= 20.0.0. Ensure the apps/server runtime (and CI) uses Node >=20; otherwise this bump could break installs or runtime.
• Run full test suite and integration tests that exercise Redis interactions to verify behavior after the minor upgrade.
• Reinstall dependencies (pnpm install) and verify lockfile integrity locally/CI to avoid mismatches.

TL;DR: Bumped Redis (and associated @redis packages) from 6.0.1 → 6.1.0 and refreshed lockfile and several tooling deps. Verify Node >=20 compatibility and run tests.

You can generate a new summary by commenting @diffy-bot.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	redis@​6.1.0

View full report

[diffy-bot]

Summary of changes

• Bumped redis dependency from ^6.0.1 to ^6.1.0 in apps/server/package.json.
• Updated pnpm lockfile (pnpm-lock.yaml) to match the redis upgrade and refreshed several transitive package versions and integrity hashes.

Files changed: 2

• apps/server/package.json
• pnpm-lock.yaml

Key details

• apps/server/package.json

  • "redis": ^6.0.1 → ^6.1.0

• pnpm-lock.yaml (high level)

  • redis: 6.0.1 → 6.1.0 (resolution integrity updated)
  • @redis/* packages: updated from 6.0.1 → 6.1.0 for:
    • @redis/bloom, @redis/client, @redis/json, @redis/search, @redis/time-series
    • Their peer/dep references updated to ^6.1.0 and matching snapshot entries adjusted.
  • Multiple other package versions bumped in the lockfile snapshots/resolutions, including:
    • baseline-browser-mapping 2.10.40 → 2.10.43
    • browserslist 4.28.4 → 4.28.6
    • caniuse-lite 1.0.30001799 → 1.0.30001806
    • electron-to-chromium 1.5.380 → 1.5.393
    • node-releases 2.0.50 → 2.0.51
  • Updated snapshots that reference the new versions (dependency trees and snapshots sections adjusted accordingly).
  • Integrity hashes for updated packages were changed to match new versions.

Impact / Action items

• Run CI/tests to ensure the redis upgrade does not break functionality.
• Install dependencies locally (pnpm install) to ensure the lockfile and node_modules are consistent.
• Verify any runtime behavior differences between redis 6.0.1 and 6.1.0 relevant to your usage (commands, client options, error handling).

Suggestions (potential issues found)

• Node engine compatibility: The pnpm lockfile entries for @redis/* (and redis packages) show engines requiring Node >= 20.0.0. If your app runs on Node 18 (or <20), this upgrade may be incompatible — confirm the runtime Node version and either:
  • Keep using redis 6.0.x, or
  • Upgrade Node to >=20 and re-run tests.
• Review changelogs for redis 6.1.0 and associated @redis/* 6.1.x packages for breaking changes or API adjustments that could affect your code.
• Because multiple transitive package versions were bumped (browserslist, caniuse-lite, etc.), run frontend/build/test flows to detect any subtle regressions.

TL;DR: Redis dependency bumped from ^6.0.1 → ^6.1.0 and pnpm lockfile updated accordingly (with several related and transitive package version bumps). Confirm Node >=20 compatibility and run full test suite.

You can generate a new summary by commenting @diffy-bot.