Skip to content

[Snyk] Upgrade fastify from 4.21.0 to 4.27.0 #353

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
Closed
lholmquist wants to merge 1 commit into from
Closed

[Snyk] Upgrade fastify from 4.21.0 to 4.27.0 #353

lholmquist wants to merge 1 commit into from

Conversation

@lholmquist
Copy link
Member

@lholmquist lholmquist commented Jun 5, 2024

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


![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)

Snyk has created this PR to upgrade fastify from 4.21.0 to 4.27.0.

ℹ️ 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 17 versions ahead of your current version.

  • The recommended version was released on a month ago.

Release notes
Package name: fastify

@snyk-bot
fix: upgrade fastify from 4.21.0 to 4.27.0
e04676c 
Snyk has created this PR to upgrade fastify from 4.21.0 to 4.27.0.

See this package in npm:
fastify

See this project in Snyk:
https://app.snyk.io/org/nodeshift-agg/project/53f94480-e7ae-41d2-985c-270fae345664?utm_source=github&utm_medium=referral&page=upgrade-pr
@lholmquist lholmquist closed this Oct 30, 2024
@lholmquist lholmquist deleted the snyk-upgrade-3957cd7152b7894b61d9566d4bad3964 branch October 30, 2024 12:31
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.

3 participants

@lholmquist @snyk-bot