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

Preparing for Fastify v5 release #1107

Closed
8 tasks done
jonnydgreen opened this issue Aug 26, 2024 · 10 comments · Fixed by #1110
Closed
8 tasks done

Preparing for Fastify v5 release #1107

jonnydgreen opened this issue Aug 26, 2024 · 10 comments · Fixed by #1110

Comments

@jonnydgreen
Copy link
Contributor

jonnydgreen commented Aug 26, 2024

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:

  • Upgrade fastify in dev deps to ^5.0.0
  • Follow fastify upgrade guide
  • Upgrade @fastify/error to ^4.0.0 (seems like this is already sorted as there is no next tag in npm? I could be wrong here!) and follow any upgrade guide
  • Upgrade @fastify/static to [next-major-version] and follow any upgrade guide
  • Upgrade @fastify/websockets to [next-major-version] and follow any upgrade guide
  • Upgrade fastify-plugin to [next-major-version] and follow any upgrade guide
  • Ensure tests run and fix anything that's necessary
  • Semver major release for all of the above

I'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):

  "devDependencies": {
-   "fastify": "^4.17.0",
+   "fastify": "next",
  },
  "dependencies": {
-    "@fastify/error": "^3.0.0",
+    "@fastify/error": "^4.0.0",
-    "@fastify/static": "^7.0.0",
+    "@fastify/static": "next",
-    "@fastify/websocket": "^10.0.0",
+    "@fastify/websocket": "next",
-    "fastify-plugin": "^4.2.0",
+    "fastify-plugin": "next",
  },

Let me know what you think so far!

@mcollina
Copy link
Collaborator

Indeed. There should be no changes that impact this directly, but I may be wrong.

voxpelli added a commit to voxpelli/mercurius that referenced this issue Sep 6, 2024
@voxpelli
Copy link
Contributor

voxpelli commented Sep 6, 2024

Trying to help out by making a PR for the above: #1110

Node engine range was already bumped in: #1109

mcollina pushed a commit that referenced this issue Sep 9, 2024
@jonnydgreen
Copy link
Contributor Author

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:

  • verify it works for the stable v5 release and update the package.json accordingly
  • then release a semver major mercurius release

If you agree, I'll update the things to do in the description and reopen this issue :)

wdyt?

@voxpelli
Copy link
Contributor

voxpelli commented Sep 9, 2024

update the package.json accordingly

This isn’t strictly needed, the current version range will include all v5 stable versions as well

then release a semver major mercurius release

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

@jonnydgreen
Copy link
Contributor Author

This isn’t strictly needed, the current version range will include all v5 stable versions as well

Yeah very true!

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

Good shout - allows us to get ahead of things!

What are your thoughts @mcollina ?

@mcollina
Copy link
Collaborator

mcollina commented Sep 9, 2024

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.

@jonnydgreen
Copy link
Contributor Author

jonnydgreen commented Sep 9, 2024

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:
Unfortunately gonna be saturday now as something came up this week

@voxpelli
Copy link
Contributor

voxpelli commented Sep 9, 2024

@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!

@jonnydgreen
Copy link
Contributor Author

jonnydgreen commented Sep 15, 2024

Quick update on this (will add more as I go through all the plugins):

  • Mercurius federation - looks like this is done, thanks @mcollina ! :)
  • Mercurius gateway - looks like this is done, thanks @mcollina ! :)
  • Mercurius auth - one of the tests is breaking with an unhandled promise rejection, looking into it!
  • Mercurius cache - looks like this is done, thanks @mcollina ! :)
  • Mercurius upload
  • Mercurius validation

@mcollina mcollina reopened this Sep 16, 2024
@mcollina
Copy link
Collaborator

All done

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 a pull request may close this issue.

3 participants