GeezerVison

Thanks for putting this together @nschonni!
And based on:

@sxa had some suggestions on dropping x390, so those are includedd

since they're captured in here I'm happy not to have my PR merged for 25 and stick with it changing from v26 :-)

Thanks, I've updated the title to reflect the new date, but haven't updated the JSON till it gets cleared up

The release v26.0.0 has been postponed once again, this time to May 4, 2026 (see nodejs/node#62526 (comment))

The May 4 date was a typo/mistake, the correct date is May 5, 2026. The linked comment has been updated to reflect that.

The May 4 date was a typo/mistake, the correct date is May 5, 2026. The linked comment has been updated to reflect that.

Fixed in the comment section too :-)

We've also developed a fix for the underlying issue (specific to the macos universal binaries included in the .pkg file) so I would expect we will be able to get it out next Tuesday without additional problems 🤞🏻

https://unofficial-builds.nodejs.org/logs/202605051424-v26.0.0/ is running

Not sure why one of the .0 is being dropped on the Debian images, but I'll manually fix it once the SHASUM is ready

Hi @nschonni!

Please check:

docker-node/.github/workflows/build-test.yml

Lines 96 to 97 in 6f8bcd7

	- name: Test for yarn
	run: docker run --rm node:${{ matrix.version }}-${{ matrix.variant }} yarn --version

This will fail if there is no yarn installed

node:internal/modules/cjs/loader:1478
  throw err;
  ^

Error: Cannot find module '/yarn'

I'll try adding this to the job step if: matrix.version < 26

I'm marking this as ready, but I'm taking a look

(re-)running ./update.sh in this branch now produces correct results. Yarn is removed everywhere and the version is correctly set to 26.0.0

It appears that the automation is not tolerant of Node.js publication errors & inconsistencies on https://nodejs.org/download/release/

(re-)running ./update.sh in this branch now produces correct results. Yarn is removed everywhere and the version is correctly set to 26.0.0

It appears that the automation is not tolerant of Node.js publication errors & inconsistencies on https://nodejs.org/download/release/

Was plaing around with the index.json, but didn't get it working entirely $(curl -sSL --compressed "${baseuri}/index.json" | jq -r '.[].version | select(test("v${version}."))').

Re-ran the scripts to fix the Yarn again

I'm seeing a v26.1.0 release in preparation for release May 7, 2026. This should not affect this PR - just noting here for awareness!

@nschonni Are you happy with this PR now? Shall we get it merged and get 26.0.0 published or is there anything else that would block that now?

Created PR on the official-images repo (docker-library/official-images#21395). See https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what if you are wondering when it will be available on the Docker Hub.

Sorry, missed your comment @sxa 😅 I assumed he was since he requested review

Thanks!
docker-library/official-images#21395 has been created :-)

No worries, I'm usually good landing my own stuff once there is another review, but since it's the first in a major, I just left it for an extra set of eyes.

docker-library/official-images#21395 is now merged, so the build process has started 🎉

Maybe it is just me but it appears that node:26-alpine was compiled without temporal enabled:

root@sv:~# docker run --rm -it --pull always node:26-alpine node -e "console.log(Temporal)"
26-alpine: Pulling from library/node
d17f077ada11: Already exists 
4dcf4452caaa: Pull complete 
4ea5683016df: Pull complete 
Digest: sha256:30f5a66e7265ef70aac56b4753ffa7905e54eca1084bc25503893ad8e9273f05
Status: Downloaded newer image for node:26-alpine
[eval]:1
console.log(Temporal)
            ^

ReferenceError: Temporal is not defined
    at [eval]:1:13
    at runScriptInThisContext (node:internal/vm:219:10)
    at node:internal/process/execution:483:12
    at [eval]-wrapper:6:24
    at runScriptInContext (node:internal/process/execution:481:60)
    at evalFunction (node:internal/process/execution:315:30)
    at evalTypeScript (node:internal/process/execution:327:3)
    at node:internal/main/eval_string:71:3

Node.js v26.0.0

Works using 26-slim:

root@sv:~# docker run --rm -it --pull always node:26-slim node -e "console.log(Temporal)"
26-slim: Pulling from library/node
e4fb5f1cd4d4: Pull complete 
acea7ddbcf53: Pull complete 
96ed2003148c: Pull complete 
f75d3309a4dd: Pull complete 
Digest: sha256:ccd1c33b2876c07564b3fae7f6a5815aa42f71163faf07d00a9907e398d48bdc
Status: Downloaded newer image for node:26-slim
Object [Temporal] {}

Having that issue with node:26-alpine3.22 and node:26-alpine3.23 as well as amd64 and ARM.
Is this a limitation by muslibc?

This comment says that there may be outdated images but that does not seem to be related as the images are seemingly pulled correctly and state that they are using Node.js 26.

@nikeee This definitely seems to be an issue with the Alpine build and not with out-to-date images (that only happens on the floating tags). To not pollute things here further I've opened #2486 to track this.