Repository navigation
build-automation waits for unused musl builds from unofficial-builds #2646
Description
Situation
After release of Node.js 26.11.0 on 2026-10-07 14:43 UTC, the automatic-updates workflow logs:
Run actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3
22.23.3
24.21.0
26.10.0
Skipping version 26.11.0 - no musl build available yet.
No versions with musl builds were updated.waiting for musl builds that are available.
Assessment
https://nodejs.org/download/release/index.json shows that the Node.js 26.11.0 release includes linux-x64-musl:
{
"version": "v26.11.0",
"date": "2026-10-07",
"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": false
},Dockerfile-alpine.template requires
"https://nodejs.org/dist/v$NODE_VERSION/node-v$NODE_VERSION-linux-$ARCH-musl.tar.xz"
Running ./update.sh 26 shows
$ ./update.sh 26
Updating version 26...
26/alpine3.23/Dockerfile updated!
26/alpine3.24/Dockerfile updated!
26/bookworm/Dockerfile updated!
26/trixie/Dockerfile updated!
26/bookworm-slim/Dockerfile updated!
26/trixie-slim/Dockerfile updated!
Done!with no warning error about missing musl files. At the time of testing, there are no musl files on https://unofficial-builds.nodejs.org/download/release/v26.11.0/
build-automation.mjs however still contains the logic to wait for musl builds from https://unofficial-builds.nodejs.org/download/release/index.json unless it is a security release, which is not the case for Node.js 26.11.0
Changes needed
The logic in build-automation.mjs to wait for musl builds needs to be removed. They are no longer being pulled from https://unofficial-builds.nodejs.org and waiting causes an unnecessary delay.
There are also discussions to pause, move or even retire https://unofficial-builds.nodejs.org, so if those plans are executed, it would prevent publication of node-docker images entirely.
Activity
MikeMcC399 commentedon Oct 8, 2026
@nschonni
Is this something you would want to address as a continuation of what you already started? If not, I can take a look.
nschonni commentedon Oct 8, 2026
I'll try and take a look, but this stuff tends to be "minor" in that I'm not bothered if I work on something that doesn't end up landing
MikeMcC399 commentedon Oct 9, 2026
I'll submit a PR for this, since it sounds like I wouldn't be duplicating anything that you already had prepared. Perhaps we'll be able to get this in place before the next Node.js 24.x release? I guess that would be soon, although I don't see anything queued up at the moment.
MikeMcC399 commentedon Oct 9, 2026
See PR #2649 to fix this issue