Update for Node.js v7.10.1. Fixes #456.

[chorrell]

Note that we had to resurrect 7.10/ to include the v7.10.1 security fix.

See:

• https://nodejs.org/en/blog/release/v7.10.1/
• https://nodejs.org/en/blog/vulnerability/july-2017-security-releases/

[chorrell]

This should land after #455 to avoid any conflicts in generate-stackbrew-library.sh

Also this includes the npm install && npm cache clean --force update.

[chorrell]

OK, the yarn version should be 0.24.4 now

[SimenB]

@chorrell can this land as soon as CI is green, or should it be rebased on master, and then new CI?

[SimenB]

CI is green. @nodejs/docker can this be merged, or should it get a rebase first?

[SimenB]

Since it's a security patch, I'll just go for it. Sorry if it's against some protocol!

[SimenB]

Docker hub PR: docker-library/official-images#3181

[chorrell]

Yeah, a merge is fine. That's what we normally do.

[SimenB]

Should we remove it again? It really slows down CI

[chorrell]

Maybe just remove 7.10 from .travis.yml for now and then remove the 7.10 directory in a month or so.

[chorrell]

#461

[ozbillwang]

But I still don't see the tag node:7 in the official hub site. One of my projects running in node 7.2, my first task is not to upgrade to node:8, but run it in node:7 images, how can I do that?

[PeterDaveHello]

@ozbillwang we only maintain LTS and the latest stable version here, so you might wanna try v8 and v9, thanks.

[SimenB]

Even if it's not in the docs, it's still available:

$ docker pull node:7
7: Pulling from library/node
ad74af05f5a2: Already exists
2b032b8bbe8b: Already exists
a9a5b35f6ead: Already exists
3245b5a1c52c: Already exists
afa075743392: Already exists
9fb9f21641cd: Already exists
3f40ad2666bc: Pull complete
49c0ed396b49: Pull complete
Digest: sha256:af5c2c6ac8bc3fa372ac031ef60c45a285eeba7bce9ee9ed66dad3a01e29ab8d
Status: Downloaded newer image for node:7
$ docker run --rm node:7 node --version
v7.10.1