Lts/* currently uses node 8, it should use node 10


The release schedule:


The documentation states: lts/* latest LTS Node.js release

It could be a different strategy is actually used, in that case the documentation should become something like: lts/* oldest active LTS Node.js release


According to (current as of 2018-10-26), 10.x has not yet reached the LTS status.

"v10": {
    "start": "2018-04-24",
    "lts": "2018-10-30",
    "maintenance": "2020-04-01",
    "end": "2021-04-01",
    "codename": ""

So this behavior seems correct to me.


Yeah, you are right! I must have looked at that scheme a few days ago: