What does @fastify/typescript think of this change?

I do agree on that because it might be a breaking change. If you may suggest a different destination branch I'm more than willing to change it.

You can target to next branch.

Thanks @climba03003 for the feedback. Target branch changed to next.

I changed the title to express better what this PR is doing.

Can you rebase again. It included other commit in your PR.

@climba03003 I've been finally able to rebase the pull request. Sorry but I don't feel comfortable with rebasing.

Sorry but I don't feel comfortable with rebasing.

I usually use GUI for rebasing, command would be too complicated if you don't familiar with git.

@climba03003 I don't want to go off-topic, but I'd like to know more about the GUI you're using (is it tortoise, perhaps?). I normally use this command git rebase -i HEAD~<number> but, as you said, it's not always user friendly (especially if there has been a merge).

@climba03003 I don't want to go off-topic, but I'd like to know more about the GUI you're using (is it tortoise, perhaps?). I normally use this command git rebase -i HEAD~<number> but, as you said, it's not always user friendly (especially if there has been a merge).

I use git fork. You need to use --onto if you want to change the base branch.

@climba03003 Thanks for the info, I'll take a look.
Btw, tests failed. According to logs it should not be related to my latest changes 🙄

@climba03003
can you please add the commits from master to next to have the latest fixes regarding node19 and tap 16.3.1 issues?

Uff, I think this also means that all plugins, which decorate fastifyReply need changes.

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.