Skip to content
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

fix(deps): update dependency fast-json-stringify to v6.0.1 #14438

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 17, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
fast-json-stringify 6.0.0 -> 6.0.1 age adoption passing confidence

Release Notes

fastify/fast-json-stringify (fast-json-stringify)

v6.0.1

Compare Source

What's Changed

New Contributors

Full Changelog: fastify/fast-json-stringify@v6.0.0...v6.0.1


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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jan 17, 2025
Copy link
Contributor Author

renovate bot commented Jan 17, 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nestjs/[email protected]
npm error Found: [email protected]
npm error node_modules/ts-morph
npm error   dev ts-morph@"25.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional ts-morph@"^16.0.0 || ^17.0.0 || ^18.0.0 || ^19.0.0 || ^20.0.0 || ^21.0.0 || ^24.0.0" from @nestjs/[email protected]
npm error node_modules/@nestjs/graphql
npm error   dev @nestjs/graphql@"12.2.2" from the root project
npm error   peer @nestjs/graphql@"^12.0.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/apollo
npm error     dev @nestjs/apollo@"12.2.2" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/ts-morph
npm error   peerOptional ts-morph@"^16.0.0 || ^17.0.0 || ^18.0.0 || ^19.0.0 || ^20.0.0 || ^21.0.0 || ^24.0.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/graphql
npm error     dev @nestjs/graphql@"12.2.2" from the root project
npm error     peer @nestjs/graphql@"^12.0.0" from @nestjs/[email protected]
npm error     node_modules/@nestjs/apollo
npm error       dev @nestjs/apollo@"12.2.2" 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 /tmp/renovate/cache/others/npm/_logs/2025-01-17T12_23_28_535Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-17T12_23_28_535Z-debug-0.log

@renovate renovate bot force-pushed the renovate/fast-json-stringify-6.x branch from eafd377 to bc3c9ce Compare January 17, 2025 12:23
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.

0 participants