Skip to content
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

"Stable" to "Current" #354

Closed
tleb opened this issue Apr 27, 2016 · 2 comments
Closed

"Stable" to "Current" #354

tleb opened this issue Apr 27, 2016 · 2 comments

Comments

@tleb
Copy link

tleb commented Apr 27, 2016

We will be using the Current label from here-on instead of Stable.
https://nodejs.org/en/blog/release/v6.0.0/#current-what-happened-to-stable

@ghost
Copy link

ghost commented Apr 27, 2016

Thanks for the info. We will take it into consideration.

The dist folder was restructured. Looks like we can easily support commands like n latest, n latest v0.10, n latest v4, n io latest v1, and n lts.

We would also remove the stable keyword.

@shadowspawn
Copy link
Collaborator

Fixed stable in #467
More recent and extensive comments in #522

This issue has not had any activity in over six months. It isn't likely to get acted on due to this report.

Feel free to open a new issue if it comes up again, with new information and renewed interest.

Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants