Skip to content

chore(deps): update dependency redis to v5 #15048

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 6, 2025
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 30, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
redis 4.7.0 -> 5.0.1 age adoption passing confidence

Release Notes

redis/node-redis (redis)

v5.0.1

Compare Source

v5.0.0

Compare Source

Redis Node.js Client Release Notes

🚀 New Features

🛠️ Improvements

BREAKING CHANGES

client.ft.search('index', '*', {DIALECT: 1})
  • Client Configuration:

    • keepAlive option has been split into keepAlive (boolean) and keepAliveInitialDelay (number)
    • Legacy mode is now accessed via .legacy() method instead of { legacyMode: true }
  • Command Options:

    • New API uses "proxy client" to store options instead of passing them directly to commands
    • Example: client.withCommandOptions({ ... }).get('key') instead of client.get(client.commandOptions({ ... }), 'key')
  • Connection Management:

    • client.QUIT/quit() is replaced by client.close()
    • client.disconnect() has been renamed to client.destroy()
  • Scan Iterators:

    • Now yield collections of items instead of individual items
    • Example: for await (const keys of client.scanIterator()) { ... } returns arrays of keys
  • Isolation Pool:

    • Superseded by RedisClientPool for better separation of concerns
  • Cluster Multi:

    • cluster.multi().addCommand() now requires isReadonly parameter for replica execution support
  • Boolean to Number Types:

    • Many commands now return numbers (0/1) instead of booleans for better Redis protocol alignment
    • Affects: COPY, EXPIRE, EXPIREAT, HEXISTS, HSETNX, MOVE, PEXPIRE, PEXPIREAT, PFADD, RENAMENX, SETNX, etc.
  • API Changes:

    • Many commands have updated parameter names and return types
    • Enums replaced with constants (e.g., RedisFlushModesREDIS_FLUSH_MODES)
    • Module-specific commands (JSON, Search, Time Series) have parameter restructuring

Full migration details: https://github.com/redis/node-redis/blob/master/docs/v4-to-v5.md

New Contributors


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 Apr 30, 2025
Copy link
Contributor Author

renovate bot commented Apr 30, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: typeorm@0.3.22
npm error Found: redis@5.0.1
npm error node_modules/redis
npm error   dev redis@"5.0.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional redis@"^3.1.1 || ^4.0.0" from typeorm@0.3.22
npm error node_modules/typeorm
npm error   dev typeorm@"0.3.22" from the root project
npm error   peer typeorm@"^0.3.0" from @nestjs/typeorm@11.0.0
npm error   node_modules/@nestjs/typeorm
npm error     dev @nestjs/typeorm@"11.0.0" from the root project
npm error
npm error Conflicting peer dependency: redis@4.7.0
npm error node_modules/redis
npm error   peerOptional redis@"^3.1.1 || ^4.0.0" from typeorm@0.3.22
npm error   node_modules/typeorm
npm error     dev typeorm@"0.3.22" from the root project
npm error     peer typeorm@"^0.3.0" from @nestjs/typeorm@11.0.0
npm error     node_modules/@nestjs/typeorm
npm error       dev @nestjs/typeorm@"11.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-05-05T12_17_48_871Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-05T12_17_48_871Z-debug-0.log

@coveralls
Copy link

coveralls commented Apr 30, 2025

Pull Request Test Coverage Report for Build f2b2a77b-3984-440a-9aa3-b56615e06313

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 88.936%

Totals Coverage Status
Change from base Build 3cef056f-99d8-47fd-8134-1097a41cc4d2: 0.0%
Covered Lines: 7194
Relevant Lines: 8089

💛 - Coveralls

@renovate renovate bot force-pushed the renovate/redis-5.x branch 8 times, most recently from 86bcc38 to 8ada683 Compare May 5, 2025 12:13
@renovate renovate bot changed the title chore(deps): update dependency redis to v5 chore(deps): update dependency redis to v5.0.1 May 5, 2025
@renovate renovate bot force-pushed the renovate/redis-5.x branch 2 times, most recently from 4eb842b to ba7901e Compare May 6, 2025 06:21
@renovate renovate bot changed the title chore(deps): update dependency redis to v5.0.1 chore(deps): update dependency redis to v5 May 6, 2025
@renovate renovate bot force-pushed the renovate/redis-5.x branch from ba7901e to dd09403 Compare May 6, 2025 06:24
@kamilmysliwiec kamilmysliwiec merged commit 970875e into master May 6, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants