Automated update for 25.9.0 does not produce PR for release

[MikeMcC399]

Situation

• Node.js 25.9.0 was released today Apr 1, 2026

• Workflow automatic-updates detects that there is a new version (see https://github.com/nodejs/docker-node/actions/runs/23859567041/job/69562209836)

  Run actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd
  20.20.2
  
  22.22.2
  
  24.14.1
  
  25.8.2
  
  Updating version 25...
  25/bookworm/Dockerfile is already up to date!
  25/bullseye/Dockerfile is already up to date!
  25/bullseye-slim/Dockerfile is already up to date!
  25/trixie/Dockerfile is already up to date!
  25/bookworm-slim/Dockerfile is already up to date!
  25/trixie-slim/Dockerfile is already up to date!
  25/alpine3.22/Dockerfile is already up to date!
  25/alpine3.23/Dockerfile is already up to date!
  Done!
  

• update.sh does no updates (claims "is already up to date!")

• No PR is created, no 25.9.0 release is triggered

[yosifkit]

docker-node/build-automation.mjs

Line 28 in 1288740

const { data: availableVersionsJson } = await github.request('https://nodejs.org/download/release/index.json');

Ah, this code detected that there is an update, so https://nodejs.org/download/release/index.json lists the new version, but without the release listed on https://nodejs.org/dist/, it cannot update the Dockerfiles.

It looks like the directory is there (https://nodejs.org/dist/v25.9.0/), but it doesn't show up on the listing page (likely because of caching somewhere).

[MikeMcC399]

Thanks @yosifkit !

I've passed this on through the Slack channel https://openjs-foundation.slack.com/archives/C019MGJQ8RH

[MikeMcC399]

Doing a test build of 25.9.0 manually, I can build trixie without errors.

So I'd suggest first waiting to see what the release team says and how quickly they can fix things. I don't think the release of Docker images for 25.9.0 is as urgent as for the previous security release, so I would suggest giving it another 24 hours before thinking about any manual action here.

Apart from that, it could be an improvement to the scripts if they actually recognized and logged the issue preventing update.

Edit: removed incorrect information about musl checksums.

[MikeMcC399]

There were some Cloudflare caching issues.

https://nodejs.org/dist/ now lists v25.9.0

That is not yet being picked up by https://github.com/nodejs/docker-node/actions/workflows/automatic-updates.yml
It may take a little while for the cache to be updated.

[nschonni]

Just landed the automatically opened #2440

[MikeMcC399]

@nschonni

Just landed the automatically opened #2440

Good news that the cache caught up! It looks like it has a one hour cache refresh:

$ curl -I https://nodejs.org/dist/
HTTP/2 200
date: Thu, 02 Apr 2026 08:06:14 GMT
content-type: text/html
cache-control: public, max-age=3600, s-maxage=14400
last-modified: Wed, 01 Apr 2026 14:45:07 GMT
strict-transport-security: max-age=31536000; includeSubDomains; preload
x-content-type-options: nosniff
server: cloudflare
cf-ray: 9e5e55432ca5889c-TXL

https://hub.docker.com/_/node/tags is showing all new tags created, with no OS/ARCH available as yet. I'll check again later on to see if it has managed to publish the builds.

Edit: this is also fixed now. https://hub.docker.com/_/node/tags shows the images.

[MikeMcC399]

Currently

docker pull amd64/node:25.9.0 # is successful
docker pull node:25.9.0 # errors with no matching manifest for linux/amd64 

Noted in docker-library/official-images#21156 (comment)