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

[Snyk] Upgrade fastify from 4.22.0 to 4.22.1 #73

Merged
merged 1 commit into from
Sep 22, 2023

Conversation

jlenon7
Copy link
Member

@jlenon7 jlenon7 commented Sep 22, 2023

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade fastify from 4.22.0 to 4.22.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 21 days ago, on 2023-08-31.
Release notes
Package name: fastify from fastify GitHub release notes
Commit messages
Package name: fastify
  • 8162801 Bumped v4.22.1
  • 498b17c fix: post async regression with empty body (#5008)
  • 9b3ca58 docs: typo on catch statement inside Postgrator migration example (#5007)
  • a250c39 chore: typos (#5006)
  • ced4672 docs(ecosystem): add `@ fastify/throttle` to core list (#5004)
  • 8000791 docs(ecosystem): add fastify-rabbitmq to ecosystem.md (#5000)
  • ad7ef96 chore: Bump the dev-dependencies group with 1 update (#5002)

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@jlenon7 jlenon7 merged commit fb1419d into develop Sep 22, 2023
4 checks passed
@jlenon7 jlenon7 deleted the snyk-upgrade-1c95b002793e961123d0350f04a3e965 branch September 22, 2023 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants