ci: drop Node.js 10 and 12

[darkgl0w]

Hello.

This PR aims to :

• drop Node.js version 10 whose support has ended since 04/30/2021
• drop Node.js version 12 whose support ends 04/30/2022

Checklist

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[mcollina]

Doing this is a semver-major change for all modules.

[Fdawgs]

I think it's best to hold fire on this until Fastify v4, and then drop node 10 and 12 at the same time. 😁

[darkgl0w]

I will update the PR to drop Node.js 12 at the same time and we will wait until v4 is released :d

[mcollina]

Could the workflows have a version number?

[climba03003]

Could the workflows have a version number?

Yes, and it need to manage multiple tag. e.g. 3.0.0 needs v3, v3.0 and v3.0.0 tags.

[mcollina]

I would recommend to land this a semver-major thenz

[Fdawgs]

I'm hesitant to land this and release a new major (v3) until Fastify v4. Dependabot will automatically bump all repos currently using this workflow from v2 to the new v3, thus dropping all testing for node 10 and 12 before we officially move away from them in v4.

[mcollina]

Ok, let's do this as part of the release choreograpy. Could you add it to the issue?

[climba03003]

I think node@18 will release (2022-04-19) faster than fastify@4 release cycle. I drop a Request Changes here for reminder.

[darkgl0w]

I think node@18 will release (2022-04-19) faster than fastify@4 release cycle. I drop a Request Changes here for reminder.

I will add 18 to the matrix when they cut the 18th branch.
Usually a major branch is cut before the LTS release.

(would be good if GitHub had a reminder feature :d)

[Fdawgs]

As v4 is now being worked on in the modules themselves (fastify/fastify-compress#224), maybe now is a good time to land this?

[mcollina]

We really need a way to have multiple version of our workflow.