nodejs
Node 24.x not yet marked as LTS ("Krypton") in index.json (website lists v24.10.0 as Latest LTS)
Version
Not applicable – issue concerns Node.js distribution metadata, not runtime behavior.
Platform
All platforms (observed on Windows, but affects all because index.json is global).
Subsystem
Release / Distribution metadata
What steps will reproduce the bug?
- Visit https://nodejs.org/dist/index.json
- Search for any entries for version v24.x.x
→ all of them have
"lts": false. - Visit https://nodejs.org – it lists v24.10.0 as “Latest LTS”.
- Tools that rely on index.json (Volta, nvm, fnm, etc.) still treat Node 22 ("Jod") as the current LTS.
How often does it reproduce? Is there a required condition?
Always, until the index.json is updated to include "lts": "Krypton" for Node 24 entries.
What is the expected behavior? Why is that the expected behavior?
When Node 24 is promoted to LTS (codename "Krypton"), each v24.x entry in index.json
should have an "lts" field set to "Krypton" rather than false.
Tools and automation use this field to determine the latest LTS line, so keeping it accurate ensures consistency between nodejs.org and the dist metadata.
What do you see instead?
All v24.x entries in index.json currently show "lts": false,
while the homepage lists v24.10.0 as “Latest LTS”.
The most recent version marked as LTS in index.json is still 22.21.0 ("Jod").
Additional information
Date checked: 2025-10-28
Example entry from https://nodejs.org/dist/index.json: { "version": "v24.10.0", "date": "2025-10-14", "lts": false }
Expected: { "version": "v24.10.0", "date": "2025-10-14", "lts": "Krypton" }
This discrepancy causes tools such as Volta, nvm, and fnm — which rely on index.json to determine the current LTS — to continue installing Node 22 instead of 24.
This seems like a metadata lag during the LTS promotion. Just filing it here in case the release metadata hasn’t yet been updated.
Thanks for maintaining Node.js and for your work on the release process 🙏
