You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Revise labels for new Node.js Release Schedule #847
I think this makes the little used node support labels somewhat obsolete (like lts_active), and current is not mentioned. lts_latest got used in some training material and will retain that as an alias even if do not document. Likewise, stable.
Not sure if n users will want to target the latest version after it reaches alpha? n uses the index information from https://github.com/nodejs/nodejs-dist-indexer and does not do date calculations. I am watching that repo to see if alpha/interim get added to the index.
Activity
shadowspawn commentedon Mar 5, 2026
shadowspawn commentedon Mar 11, 2026
https://nodejs.org/en/blog/announcements/evolving-the-nodejs-release-schedule
Terminology used in announcement:
shadowspawn commentedon Apr 13, 2026
My current thinking is to modify existing
currentto allow avoiding alphas:latest: highest release, may be alpha or current/active depending on timingcurrent: highest release not alpha, may be current/active or LTS depending on timinglts: highest LTS releaseI was concerned about the "new" alpha stage, but it isn't that different to the odd numbered releases.
Likewise I wonder about a warning for alpha versions, but it will be visible in the version:
shadowspawn commentedon Oct 18, 2026
Released in v11.0.0