Skip to content

fix(deps): update dependency fastify to v5 #325

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update dependency fastify to v5 #325

wants to merge 1 commit into from
+1 −1

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 18, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
fastify (source) ^4.12.0 -> ^5.0.0 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

fastify/fastify (fastify)

v5.6.2

Compare Source

v5.6.1

Compare Source

What's Changed

New Contributors

Full Changelog: fastify/fastify@v5.6.0...v5.6.1

v5.6.0

Compare Source

What's Changed

New Contributors

Full Changelog: fastify/fastify@v5.5.0...v5.6.0

v5.5.0

Compare Source

What's Changed

New Contributors

Full Changelog: fastify/fastify@v5.4.0...v5.5.0

v5.4.0

Compare Source

What's Changed

Full Changelog: fastify/fastify@v5.3.3...v5.4.0

v5.3.3

Compare Source

What's Changed
New Contributors

Full Changelog: fastify/fastify@v5.3.2...v5.3.3

v5.3.2

Compare Source

⚠️ Security Release ⚠️

Unfortunately, v5.3.1 did not include a complete fix for "Invalid content-type parsing could lead to validation bypass" and CVE-2025-32442. This is a follow-up patch to cover an edge case.

What's Changed
New Contributors

Full Changelog: fastify/fastify@v5.3.1...v5.3.2

v5.3.1

Compare Source

⚠️ Security Release ⚠️
What's Changed
New Contributors

Full Changelog: fastify/fastify@v5.3.0...v5.3.1

v5.3.0

Compare Source

What's Changed
New Contributors

Full Changelog: fastify/fastify@v5.2.2...v5.3.0

v5.2.2

Compare Source

What's Changed
New Contributors

Full Changelog: fastify/fastify@v5.2.1...v5.2.2

v5.2.1

Compare Source

What's Changed
  • chore: org members reorder by @​Eomm in #​5898
  • docs(request): clarify request host functionality by @​Fdawgs in #​5904
  • chore(package): add fdawgs to contributors array by [@​Fdawgs](h

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
Copy link
Contributor Author

renovate bot commented Sep 18, 2024 •
edited
Loading

⚠️ 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/[email protected]
npm error Found: [email protected]
npm error node_modules/fastify
npm error   fastify@"^5.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer fastify@"^4.12.0" from @nestjs/[email protected]
npm error node_modules/@nestjs/mercurius
npm error   @nestjs/mercurius@"^12.0.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/fastify
npm error   peer fastify@"^4.12.0" from @nestjs/[email protected]
npm error   node_modules/@nestjs/mercurius
npm error     @nestjs/mercurius@"^12.0.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-12-02T05_57_36_506Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-12-02T05_57_36_506Z-debug-0.log

@renovate renovate bot force-pushed the renovate/fastify-5.x branch 4 times, most recently from 7c44978 to c9af05b Compare September 25, 2024 06:16
@renovate renovate bot force-pushed the renovate/fastify-5.x branch 5 times, most recently from c7e3c39 to 7c1722d Compare September 27, 2024 22:52
@renovate renovate bot force-pushed the renovate/fastify-5.x branch 4 times, most recently from 3717f96 to c5c5109 Compare October 9, 2024 22:13
@renovate renovate bot force-pushed the renovate/fastify-5.x branch 15 times, most recently from ff70a2f to 6e2af7a Compare October 23, 2024 23:07
@renovate renovate bot force-pushed the renovate/fastify-5.x branch from 6e2af7a to 0fdeb6e Compare October 25, 2024 15:05
@renovate renovate bot force-pushed the renovate/fastify-5.x branch 4 times, most recently from 2e70552 to 120272b Compare January 18, 2025 05:30
@renovate renovate bot force-pushed the renovate/fastify-5.x branch 24 times, most recently from 73356e3 to 733197c Compare December 2, 2025 03:36
@renovate renovate bot force-pushed the renovate/fastify-5.x branch from 733197c to b780cad Compare December 2, 2025 05:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant