-
Notifications
You must be signed in to change notification settings - Fork 237
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
Preparing for Fastify v5 release #1107
Comments
Indeed. There should be no changes that impact this directly, but I may be wrong. |
Thank you for sorting this! 🚀 Apologies for the delay in replying/reviewing, was at a wedding this weekend! Before we move onto the other Mercurius plugins, I guess we need to:
If you agree, I'll update the things to do in the description and reopen this issue :) wdyt? |
This isn’t strictly needed, the current version range will include all v5 stable versions as well
I think official Fastify plugins have released new majors already, but has marked them as pre-releases in GitHub and npm, could do the same here, either that or a beta / rc release |
Yeah very true!
Good shout - allows us to get ahead of things! What are your thoughts @mcollina ? |
I'll get to this in the next couple of days, once I have everything lined up for Fastify v5. If anybody can beat me to it, it would be amazing. |
Thanks for doing the pre-release earlier! :) I've got a free day on Wednesday so I'll aim to get the mercurius plugins aligned then! @voxpelli if you wanna help out on this as well, gimme a shout :) Edit: |
@jonnydgreen Sadly not using any of the mercurius plugins, so won't come naturally, and I have a bit of a deadline right now, but generally I'm very open to contribute! |
Quick update on this (will add more as I go through all the plugins):
|
All done |
Hi! I've pre-emptively started to take a look at what's required for supporting Fastify v5. As I understand it, once Fastify v5 is released, we need to:
fastify
in dev deps to^5.0.0
fastify
upgrade guide@fastify/error
to^4.0.0
(seems like this is already sorted as there is nonext
tag in npm? I could be wrong here!) and follow any upgrade guide@fastify/static
to[next-major-version]
and follow any upgrade guide@fastify/websockets
to[next-major-version]
and follow any upgrade guidefastify-plugin
to[next-major-version]
and follow any upgrade guideI've done an initial pass to get an idea of things on my local machine using the
next
tag and all appears to be okay so far (npm run test
works with no issue), although I'll wait until the upgrade guide(s) to be 100% confident about this and I'm not fully aware of the required v5 changes :)My testing changes so far (deps removed for brevity):
Let me know what you think so far!
The text was updated successfully, but these errors were encountered: