Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 31, 2025

This PR contains the following updates:

Package Change Age Confidence
ioredis 5.6.1 -> 5.7.0 age confidence

Release Notes

luin/ioredis (ioredis)

v5.7.0

Compare Source

Bug Fixes
Features

5.6.1 (2025-04-11)

Bug Fixes
  • adding debug log on cluster.slots initial connection error (bedcfb5)

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 Jul 31, 2025
@renovate
Copy link
Contributor Author

renovate bot commented Jul 31, 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: @nestjs/graphql@13.1.0
npm error Found: ts-morph@26.0.0
npm error node_modules/ts-morph
npm error   dev ts-morph@"26.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional ts-morph@"^20.0.0 || ^21.0.0 || ^24.0.0 || ^25.0.0" from @nestjs/graphql@13.1.0
npm error node_modules/@nestjs/graphql
npm error   dev @nestjs/graphql@"13.1.0" from the root project
npm error   peer @nestjs/graphql@"^13.0.0" from @nestjs/apollo@13.1.0
npm error   node_modules/@nestjs/apollo
npm error     dev @nestjs/apollo@"13.1.0" from the root project
npm error
npm error Conflicting peer dependency: ts-morph@25.0.1
npm error node_modules/ts-morph
npm error   peerOptional ts-morph@"^20.0.0 || ^21.0.0 || ^24.0.0 || ^25.0.0" from @nestjs/graphql@13.1.0
npm error   node_modules/@nestjs/graphql
npm error     dev @nestjs/graphql@"13.1.0" from the root project
npm error     peer @nestjs/graphql@"^13.0.0" from @nestjs/apollo@13.1.0
npm error     node_modules/@nestjs/apollo
npm error       dev @nestjs/apollo@"13.1.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-08-01T07_13_36_202Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-08-01T07_13_36_202Z-debug-0.log

@coveralls
Copy link

coveralls commented Jul 31, 2025

Pull Request Test Coverage Report for Build a8ec8809-092e-40ce-8a75-cc12edd015ee

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.913%

Totals Coverage Status
Change from base Build 4dd695a8-95d0-44e4-9d87-bf29cd186d54: 0.0%
Covered Lines: 7282
Relevant Lines: 8190

💛 - Coveralls

@renovate renovate bot force-pushed the renovate/ioredis-5.x branch from 342e360 to 978b505 Compare August 1, 2025 07:13
@kamilmysliwiec kamilmysliwiec merged commit b6d4188 into master Aug 1, 2025
1 of 2 checks passed
@renovate renovate bot deleted the renovate/ioredis-5.x branch August 1, 2025 07:17
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.

3 participants