Improve documention on version input (semver spec behavior in readme)

[GMartigny]

Hi,
As far as I see, there's no way to use the latest node version without manually specifying it.
I want to be able to run my tests in the latest node version without updating it each time a new version came out.
It could be achieved with the keyword 'latest' or 'node' in the same way you can do with NVM.
Cheers

[faisaldahdal-arch]

Agreed, lets do that.

…

________________________________ From: Guillaume Martigny <notifications@github.com> Sent: Monday, June 22, 2020 4:23 AM To: actions/setup-node <setup-node@noreply.github.com> Cc: Subscribed <subscribed@noreply.github.com> Subject: [actions/setup-node] [Feature] Run latest node version (#164) Hi, As far as I see, there's no way to use the latest node version without manually specifying it. I want to be able to run my tests in the latest node version without updating it each time a new version came out. It could be achieved with the keyword 'latest' or 'node' in the same way you can do with NVM. Cheers — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#164>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APPCCMIOP6SL6TGHSYUPOM3RX4WJPANCNFSM4OEOF2BA>.

[bryanmacfarlane]

the version input is a semver version spec. So 14.x works. Doesn't * work?
https://jubianchi.github.io/semver-check/#/*/14.0.8

[GMartigny]

Doesn't * work?

Yes it does, thanks for the workaround. Maybe, this solution should be more promoted on the action documentation.
Thanks again

[bryanmacfarlane]

@GMartigny - thanks, I'll re-open and morph to a doc issue. One small note - it's not a workaround ;) the semver spec is a feature and the way we believe it should work. I'll update the readme.

[dmitry-shibanov]

Hello @GMartigny. We added section about supported version syntax to the docs. I think it should cover the logic about semver notation and getting latest available versions from node-versions.
But I want to notice that according to the docs, if you use check-latest input, the action firstly will check versions from node-versions repository and if the version is not found it'll fallback to the toolcache. The input lts/* will help to grab appropriate LTS version.

[GMartigny]

If I understand correctly, lts/* is equivalent to latest ?

[dmitry-shibanov]

Hello @GMartigny. The latest input can install non lts version, which is now 17, and the lts/* input will download the lts version, which is now 16.