Repository navigation
lts tag applied to wrong version Node.js 26.12.1 #2671
Description
Situation
docker-library/official-images#22615 was opened with lts tags applied to Node.js 26.12.1
This is not an lts release.
https://nodejs.org/download/release/index.json is the source of truth and the lts key is set to false
{
"version": "v26.12.1",
"date": "2026-10-21",
"files": [
"aix-ppc64",
"headers",
"linux-arm64",
"linux-ppc64le",
"linux-s390x",
"linux-x64",
"linux-x64-musl",
"osx-arm64-tar",
"osx-x64-pkg",
"osx-x64-tar",
"src",
"win-arm64-7z",
"win-arm64-zip",
"win-x64-7z",
"win-x64-exe",
"win-x64-msi",
"win-x64-zip"
],
"npm": "11.20.0",
"v8": "14.6.202.34",
"uv": "1.52.1",
"zlib": "1.3.2.1-motley",
"openssl": "3.5.9",
"modules": "147",
"lts": false,
"security": true
},
Activity
nschonni commentedon Oct 28, 2026
Script uses the set date in
docker-node/versions.json
Line 4 in a1b5cb2
Not a bug, but the
stackbrew.jscould be rewritten to make direct calls for to theindex.jsonMikeMcC399 commentedon Oct 29, 2026
This shouldn't cause a problem until next LTS transition in October 2027. Nevertheless it would be better for
index.jsonto be used. The dates aren't reliable, only a guideline.ltsis eitherfalseor it contains the code name of the release, for example "Lithium".Using
index.jsonwould avoid also have to duplicate the code names locally.