"npm install node@lts" reports 12.18.1 which does not match 12.18.2 listed on website

[mlandisbqs]

• Version: v12.18.1
• Platform: MacOS 10.15.4 (Darwin WAHVE-WKS04.piholio 19.4.0 Darwin Kernel Version 19.4.0: Wed Mar 4 22:28:40 PST 2020; root:xnu-6153.101.6~15/RELEASE_X86_64 x86_64)
• Subsystem: ???

What steps will reproduce the bug?

$ npm install -g --dry-run node@lts
+ node@12.18.1
added 2 packages in 0.247s

How often does it reproduce? Is there a required condition?

Consistently outputs 12.18.1 every time

What is the expected behavior?

+ node@12.18.2  # <-- 12.18.2 is the version listed on the site https://nodejs.org/en/

What do you see instead?

+ node@12.18.1

Additional information

Context - my team parses the dryrun output in our build to make sure that our project keeps up with LTS.
We're currently 1 version behind LTS - probably not a big deal but it could become a problem over time if this isn't fixed.

[richardlau]

You'll have to report that to the owner of the node module, https://github.com/aredridel/node-bin-gen according to its npm page.

[mlandisbqs]

In case anyone lands here, moved: aredridel/node-bin-gen#103 per comment.