• The devDependency tap was updated from 12.7.0 to 13.1.2.

Update to this version instead 🚀

• The devDependency tap was updated from 12.7.0 to 13.1.3.

Update to this version instead 🚀

• The devDependency tap was updated from 12.7.0 to 13.1.5.

Update to this version instead 🚀

• The devDependency tap was updated from 12.7.0 to 13.1.6.

Update to this version instead 🚀

• The devDependency tap was updated from 12.7.0 to 13.1.7.

Update to this version instead 🚀

• The devDependency tap was updated from 12.7.0 to 13.1.8.

Update to this version instead 🚀

For Your Info: in fastify-example I had some problems with the upgrade to Tap 13.x, but with with today release (13.1.8) all has been solved (thanks to the help Tap guys gave me), but I had to add in npm custom commands the flag '--no-esm', no sure it will be needed even here.

@mcollina @delvedor I can do some check, but for a PR (if needed) on which branch, a new one to arget this or from/to master ?
Last in my test commands I force even a '--strict' flag, do you think it would be useful even here ?

Thanks. Bye, Sandro

@smartiniOnGitHub tap v13 has dropped node v6 (that we are still supporting), so we can't upgrade this dev-dept.

In this case we should add tap in the greenkeeper ignore list (in package.json) and close this PR
Would you like to do so?

@Eomm ok I can do, in a new PR for that change, right ?
Last, sorry for next major release (3.x, should be in a 'next' branch or similar) there should be already a plan to remove Node.js 6.x, right ? Or an issue is needed ?

ok I can do, in a new PR for that change, right ?

Yes 👍

there should be already a plan to remove Node.js 6.x, right ?

Yes also here

Or an issue is needed ?

Nope, I'm not sure, but I think the leads will open it to discuss and define the tasks in future. (for notice: there are already some issue with the v3 label)

Last, sorry for next major release (3.x, should be in a 'next' branch or similar) there should be already a plan to remove Node.js 6.x, right ? Or an issue is needed ?

Yes we'll drop Node 6 then.
I've cut a new branch next. Would you like to send a PR?

@mcollina Ciao Matteo, sure but maybe before a PR an issue would be good, to better define what it means ? At the moment I think of: removing it from all CI systems, update docs, etc but maybe there are some code portions that should be updated too (and for this I'm not aware). Thanks for now. Bye

All of that, plus removing some of the conditionals for async/await and http2 in the tests.

Hi all, PR done: #1643
In next days I'll the other (maybe even the removal of some dependencies in GreenKeeper to target as minimum Node.js 8.x in the 'next' branch) ... Bye

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.