fix: updated fastify to version 5 #610
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ajitsinghkaler
force-pushed
the
fastify-update
branch
from
a2484c8 to
40523a6
Compare
ajitsinghkaler
force-pushed
the
fastify-update
branch
from
40523a6 to
1aebef7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Fastify 4 is EOL at 2025-06-30. So updated fastify 4 to 5 to get to the latest version of fastify also to support version 5 node 20 is needed so updated node version to 20 too.
What is the current behavior?
Currently the repo uses fastify 4. Which also supports node 14.
What is the new behavior?
The repo will be updated to fastify 5. Updated node version to 20.