cc @maxim-lobanov

I'd like to request that 'latest' also be supported, however even without it this would be great to have! Thank you for making the PR

I'd like to request that 'latest' also be supported, however even without it this would be great to have! Thank you for making the PR

Done! 👍
I also added the latest alias in addition to the current one.

Dowload ?

From #278 (comment)

We will be ready to cut new action release at the begin of next week.

Could you review this PR and maybe include it in the next release if possible and everything is good to go, please ? 😄 @maxim-lobanov

any chance to merge this?

Hi,
It's been two months: is there any news about this PR?

Thanks for your interest. @Kikobeats and @demurgos

I'm happy to continue to work on this PR if it's needed.
The main problem currently is that it is not caching the Node.js version, it's downloading again Node.js even if the current release hasn't changed.
That means it's slower than it should be, at least it works. 😄
But to set up caching, I would need some help from the maintainers.

Hello @divlo. Thank you for your pull request. Could please attach link to the documentation for the current alias ? If I understood well, it should install the latest (lts/non lts) version ? My main concern is about that the latest alias is more obvious.

Hello @divlo. Thank you for your pull request. Could please attach link to the documentation for the current alias ? If I understood well, it should install the latest (lts/non lts) version ? My main concern is about that the latest alias is more obvious.

Updated README and resolved the conflicts. 👍
Yes, it installs the latest Node.js version (for example currently it is v17.3.1).
The latest alias might be more obvious but the real name is current as you can see on the Node.js website.

Just a memory dump of prior art:

• current is the official terminology as per https://nodejs.org/en/about/releases/
• nvm does not support current or latest, but it does support node (and a deprecated alias for that: stable).
• Travis CI (reference CI for a very long time in the Node.js ecosystem) does support latest (and pulls in the "current (stable) release"), but I think it does that because it installs node via nvm when the keyword is unsupported, rather than latest being explicitly supported (if I remember correctly from the research I did for https://github.com/pkgjs/detect-node-support)
• https://github.com/pkgjs/nv (reference package from https://github.com/nodejs/package-maintenance WG) supports current (alias meaning the same as node from nvm)

I'd argue latest should not be supported explicitly.

Could it be that the two would exists ? "current" and "latest" being synonyms ?

My thinking is that "latest" can be misleading, esp. in the context of there being "latest in a release line", "latest LTS", etc. I'd rather have latest not work and error out, so that people do not pick that up and try to use it elsewhere, eventually leading to further confusion.

I could be wrong in my thinking, of course. I'll try to dig out some more discussion threads about this for reference.

I guess a lot of threads can be followed from nodejs/package-maintenance#236

I do have to admit, that I have an issue open on nvm side to support latest myself, but ideally these keywords should all be converging...

@dmitry-shibanov Friendly ping. 😄

What is needed to merge this PR?

Just a memory dump of prior art:

• current is the official terminology as per https://nodejs.org/en/about/releases/
• nvm does not support current or latest, but it does support node (and a deprecated alias for that: stable).
• Travis CI (reference CI for a very long time in the Node.js ecosystem) does support latest (and pulls in the "current (stable) release"), but I think it does that because it installs node via nvm when the keyword is unsupported, rather than latest being explicitly supported (if I remember correctly from the research I did for https://github.com/pkgjs/detect-node-support)
• https://github.com/pkgjs/nv (reference package from https://github.com/nodejs/package-maintenance WG) supports current (alias meaning the same as node from nvm)

I'd argue latest should not be supported explicitly.

so does actions/setup-node support node too?

@bluelovers Does node alias is about the latest current Node.js released version (e.g: currently it is v17.5.0)?
If yes, that would solve this issue, but it just adds another naming...
What naming should we choose: current or latest or node or all the three together?

@bluelovers Does node alias is about the latest current Node.js released version (e.g: currently it is v17.5.0)? If yes, that would solve this issue, but it just adds another naming... What naming should we choose: current or latest or node or all the three together?

nvm , travis ci use node , and actions/setup-node support nvmrc, so i think node should be support

This PR has no recent activity, and probably won't be merged for a long time and as I don't want/have time to do the job for this PR, I decided to close it.

Feel free to open another PR yourself based on this one if you want this to be implemented.