-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support latest
as a version alias for the latest Node version
#257
Comments
Amended Readme.md removing unnecessary brackets and update Nodejs to Nodejs LTS Amended GitHub Actions node.js.yml to use nodejs lts version 14 (As of 26 May 2021 as currently there are still some issues supporting `lts` alias in `setup-node` GitHub Action which is a known issue: actions/setup-node#26 actions/setup-node#257)
Good news! PR available there: #279 |
1 year of discussions, do we have a chance? |
Hi @zdm, Yes, this feature is under development. |
Hello everyone, we released a new version of the setup-node action with support of latest alias. For now I'm going to close the issue. If you have any concerns feel free to ping us. |
#26 discusses supporting several types of aliases. That discussion has been going on for a long time. It seems the main complications revolve around how to deal with
lts
.For those of us who don't care about
lts
and just wantlatest
so that we can test that our work works on latest Node automatically, could we please get support forlatest
first and let #26 focus on the subtleties oflts
and how to implement that? It seems like these two aliases do not need to be grouped into a single feature release, in fact, it looks, like implementing them separately would simplify things and potentially make it possible to providelatest
soon.The text was updated successfully, but these errors were encountered: