Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 28, 2025

This PR contains the following updates:

Package Change Age Confidence
@types/express (source) 5.0.4 -> 5.0.5 age confidence

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

renovate bot commented Oct 28, 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 warn ERESOLVE overriding peer dependency
npm warn While resolving: @apollo/client@3.11.10
npm warn Found: graphql-ws@6.0.6
npm warn node_modules/graphql-ws
npm warn   graphql-ws@"6.0.6" from @nestjs/graphql@13.2.0
npm warn   node_modules/@nestjs/graphql
npm warn     dev @nestjs/graphql@"13.2.0" from the root project
npm warn     1 more (@nestjs/apollo)
npm warn
npm warn Could not resolve dependency:
npm warn peerOptional graphql-ws@"^5.5.5" from @apollo/client@3.11.10
npm warn node_modules/@apollo/client
npm warn   optional @apollo/client@"~3.2.5 || ~3.3.0 || ~3.4.0 || ~3.5.0 || ~3.6.0 || ~3.7.0 || ~3.8.0 || ~3.9.0 || ~3.10.0 || ~3.11.0 || ~3.12.0 || ~3.13.0" from graphql-tools@9.0.20
npm warn   node_modules/graphql-tools
npm warn
npm warn Conflicting peer dependency: graphql-ws@5.16.2
npm warn node_modules/graphql-ws
npm warn   peerOptional graphql-ws@"^5.5.5" from @apollo/client@3.11.10
npm warn   node_modules/@apollo/client
npm warn     optional @apollo/client@"~3.2.5 || ~3.3.0 || ~3.4.0 || ~3.5.0 || ~3.6.0 || ~3.7.0 || ~3.8.0 || ~3.9.0 || ~3.10.0 || ~3.11.0 || ~3.12.0 || ~3.13.0" from graphql-tools@9.0.20
npm warn     node_modules/graphql-tools
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @apollo/server-plugin-landing-page-graphql-playground@4.0.1
npm warn Found: @apollo/server@5.0.0
npm warn node_modules/@apollo/server
npm warn   dev @apollo/server@"5.0.0" from the root project
npm warn   2 more (@as-integrations/express5, @nestjs/apollo)
npm warn
npm warn Could not resolve dependency:
npm warn peer @apollo/server@"^4.0.0" from @apollo/server-plugin-landing-page-graphql-playground@4.0.1
npm warn node_modules/@apollo/server-plugin-landing-page-graphql-playground
npm warn   @apollo/server-plugin-landing-page-graphql-playground@"4.0.1" from @nestjs/apollo@13.2.1
npm warn   node_modules/@nestjs/apollo
npm warn
npm warn Conflicting peer dependency: @apollo/server@4.12.2
npm warn node_modules/@apollo/server
npm warn   peer @apollo/server@"^4.0.0" from @apollo/server-plugin-landing-page-graphql-playground@4.0.1
npm warn   node_modules/@apollo/server-plugin-landing-page-graphql-playground
npm warn     @apollo/server-plugin-landing-page-graphql-playground@"4.0.1" from @nestjs/apollo@13.2.1
npm warn     node_modules/@nestjs/apollo
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nestjs/graphql@13.2.0
npm error Found: ts-morph@27.0.2
npm error node_modules/ts-morph
npm error   dev ts-morph@"27.0.2" 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.2.0
npm error node_modules/@nestjs/graphql
npm error   dev @nestjs/graphql@"13.2.0" from the root project
npm error   peer @nestjs/graphql@"^13.0.0" from @nestjs/apollo@13.2.1
npm error   node_modules/@nestjs/apollo
npm error     dev @nestjs/apollo@"13.2.1" 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.2.0
npm error   node_modules/@nestjs/graphql
npm error     dev @nestjs/graphql@"13.2.0" from the root project
npm error     peer @nestjs/graphql@"^13.0.0" from @nestjs/apollo@13.2.1
npm error     node_modules/@nestjs/apollo
npm error       dev @nestjs/apollo@"13.2.1" 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-10-28T01_31_45_512Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-28T01_31_45_512Z-debug-0.log

@coveralls
Copy link

Pull Request Test Coverage Report for Build 3a776f74-64a1-4818-ac46-c633318b3ead

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

Totals Coverage Status
Change from base Build 41948611-fb3c-41dc-8c91-41ac693b5c67: 0.0%
Covered Lines: 7324
Relevant Lines: 8236

💛 - Coveralls

@renovate renovate bot force-pushed the renovate/express-5.x branch from d14ab26 to 27c0c41 Compare October 28, 2025 08:29
@kamilmysliwiec kamilmysliwiec merged commit dabf31f into master Oct 28, 2025
4 checks passed
@renovate renovate bot deleted the renovate/express-5.x branch October 28, 2025 09:55
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