fix(deps): update dependency cache-manager-redis-store to v3

renovate[bot] commented 1 year ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
cache-manager-redis-store	`2.0.0` -> `3.0.1`

Release Notes

dabroek/node-cache-manager-redis-store

### [`v3.0.1`](https://togithub.com/dabroek/node-cache-manager-redis-store/blob/HEAD/CHANGELOG.md#v301---17-Oct-2022) [Compare Source](https://togithub.com/dabroek/node-cache-manager-redis-store/compare/v3.0.0...v3.0.1) Fixed bug where the `redisStore.del` would no longer accept an options object, which broke the multiCaching interface. ### [`v3.0.0`](https://togithub.com/dabroek/node-cache-manager-redis-store/blob/HEAD/CHANGELOG.md#v300---15-Oct-2022) [Compare Source](https://togithub.com/dabroek/node-cache-manager-redis-store/compare/v2.0.0...v3.0.0) Upgraded to redis@^4 ##### Breaking Changes - The store needs to be instantiated before passing it to cache-manager and can no longer be instantiated with the factory method - Dropped support for Node.js < 16.18

Configuration

📅 Schedule: 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 becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 1 year ago

⚠ 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 ERESOLVE overriding peer dependency
npm WARN While resolving: @nestjs/mapped-types@1.2.0
npm WARN Found: class-validator@0.14.0
npm WARN node_modules/class-validator
npm WARN   class-validator@"^0.14.0" from the root project
npm WARN   2 more (@nestjs/common, @nestjs/swagger)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peerOptional class-validator@"^0.11.1 || ^0.12.0 || ^0.13.0" from @nestjs/mapped-types@1.2.0
npm WARN node_modules/@nestjs/mapped-types
npm WARN   @nestjs/mapped-types@"1.2.0" from @nestjs/swagger@6.1.4
npm WARN   node_modules/@nestjs/swagger
npm WARN 
npm WARN Conflicting peer dependency: class-validator@0.13.2
npm WARN node_modules/class-validator
npm WARN   peerOptional class-validator@"^0.11.1 || ^0.12.0 || ^0.13.0" from @nestjs/mapped-types@1.2.0
npm WARN   node_modules/@nestjs/mapped-types
npm WARN     @nestjs/mapped-types@"1.2.0" from @nestjs/swagger@6.1.4
npm WARN     node_modules/@nestjs/swagger
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: typeorm@0.3.11
npm ERR! Found: mssql@9.0.1
npm ERR! node_modules/mssql
npm ERR!   mssql@"^9.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional mssql@"^7.3.0" from typeorm@0.3.11
npm ERR! node_modules/typeorm
npm ERR!   typeorm@"^0.3.11" from the root project
npm ERR!   peer typeorm@"^0.3.0" from @nestjs/typeorm@9.0.1
npm ERR!   node_modules/@nestjs/typeorm
npm ERR!     @nestjs/typeorm@"^9.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: mssql@7.3.5
npm ERR! node_modules/mssql
npm ERR!   peerOptional mssql@"^7.3.0" from typeorm@0.3.11
npm ERR!   node_modules/typeorm
npm ERR!     typeorm@"^0.3.11" from the root project
npm ERR!     peer typeorm@"^0.3.0" from @nestjs/typeorm@9.0.1
npm ERR!     node_modules/@nestjs/typeorm
npm ERR!       @nestjs/typeorm@"^9.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2023-01-12T14_51_59_930Z-debug-0.log

renovate[bot] commented 1 year ago

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade and you will not receive PRs for any future 3.x releases. However, if you upgrade to 3.x manually then Renovate will reenable minor and patch updates automatically.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

UK-Export-Finance / nestjs-template