Skip to content

fix(deps): update nest-graphql monorepo to v13.3.0#16832

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/nest-graphql-monorepo
Open

fix(deps): update nest-graphql monorepo to v13.3.0#16832
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/nest-graphql-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 22, 2026

This PR contains the following updates:

Package Change Age Confidence
@nestjs/apollo 13.2.513.3.0 age confidence
@nestjs/graphql 13.2.513.3.0 age confidence
@nestjs/mercurius 13.2.513.3.0 age confidence

Release Notes

nestjs/graphql (@​nestjs/apollo)

v13.3.0

Compare Source

13.3.0 (2026-04-22)

Bug fixes
Enhancements
Dependencies
Committers: 3

Configuration

📅 Schedule: (UTC)

  • 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 these updates 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 22, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 22, 2026

⚠️ 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. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @typescript-eslint/eslint-plugin@8.59.0
npm error Found: @typescript-eslint/parser@8.58.2
npm error node_modules/@typescript-eslint/parser
npm error   dev @typescript-eslint/parser@"8.58.2" from the root project
npm error   @typescript-eslint/parser@"8.58.2" from typescript-eslint@8.58.2
npm error   node_modules/typescript-eslint
npm error     dev typescript-eslint@"8.58.2" from the root project
npm error   1 more (@typescript-eslint/eslint-plugin)
npm error
npm error Could not resolve dependency:
npm error peer @typescript-eslint/parser@"^8.59.0" from @typescript-eslint/eslint-plugin@8.59.0
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   dev @typescript-eslint/eslint-plugin@"8.59.0" from the root project
npm error
npm error Conflicting peer dependency: @typescript-eslint/parser@8.59.0
npm error node_modules/@typescript-eslint/parser
npm error   peer @typescript-eslint/parser@"^8.59.0" from @typescript-eslint/eslint-plugin@8.59.0
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"8.59.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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/2026-04-22T11_31_20_459Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-22T11_31_20_459Z-debug-0.log

@coveralls
Copy link
Copy Markdown

Coverage Report for CI Build 0

Coverage remained the same at 89.965%

Details

  • Coverage remained the same as the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 8520
Covered Lines: 7665
Line Coverage: 89.96%
Relevant Branches: 2878
Covered Branches: 2332
Branch Coverage: 81.03%
Branches in Coverage %: No
Coverage Strength: 56.42 hits per line

💛 - Coveralls

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.

1 participant