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

Documentation is not clear on whether lts/* refers to the Active LTS or Current LTS version #3510

Open
tamoreton opened this issue Jan 17, 2025 · 1 comment

Comments

@tamoreton
Copy link

tamoreton commented Jan 17, 2025

My reading of Node.js — Node.js Releases:

There are three phases that a Node.js release can be in: 'Current', 'Active Long Term Support (LTS)', and 'Maintenance'. Odd-numbered release lines are not promoted to LTS - they will not go through the 'Active LTS' or 'Maintenance' phases.

  • Current - Should incorporate most of the non-major (non-breaking) changes that land on nodejs/node main branch.
  • Active LTS - New features, bug fixes, and updates that have been audited by the Release team and have been determined to be appropriate and stable for the release line.
  • Maintenance - Critical bug fixes and security updates. New features may be added at the discretion of the Release team - typically only in cases where the new feature supports migration to later release lines.

is that unless you're a library author, you should probably be using the Active LTS version of Node rather than the Current LTS.

The nvm docs say that lts/* refers to the "latest" LTS, but it's ambiguous (to me) whether that means the latest Active LTS version or the latest Current LTS version.

@ljharb
Copy link
Member

ljharb commented Jan 17, 2025

“Current” isn’t LTS at all.

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

No branches or pull requests

2 participants