Gürgün Dayıoğlu

I think in `next` we should fix the type instead and it should be undefined again

I fixed it with https://github.com/fastify/fastify/commit/35a6b999bb719d53d1da58374bff1718694da66e

> Note: we must pin [email protected] for any projects utilizing it. Should we pin specifically to `[email protected]` or is `^16` sufficient?

Also, maybe we can also work on centralizing all CI workflows (and possibly most scripts) during this release cycle I see that some repos use [`plugins-ci`](https://github.com/fastify/fastify-multipart/blob/master/.github/workflows/ci.yml), which is great, but...

fastify-dx is archived, it can be marked as done

I think long term `node:test` looks amazing and for me is delightful to use, but I agree that it's too much work right now

Go for it!

@Uzlopak is busy at the moment AFAIK, so someone could take over I think I can look at this after Wednesday

I really like this change, and I believe nothing serious is blocking this? Can we get this merged soon?

@climba03003 when can you rebase this? I can do some solid simplification after this PR