You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Automated update for 25.9.0 does not produce PR for release #2439
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!")
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).
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.
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.
Activity
yosifkit commentedon Apr 1, 2026
docker-node/build-automation.mjs
Line 28 in 1288740
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 commentedon Apr 1, 2026
Thanks @yosifkit !
I've passed this on through the Slack channel https://openjs-foundation.slack.com/archives/C019MGJQ8RH
MikeMcC399 commentedon Apr 1, 2026
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 commentedon Apr 1, 2026
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 commentedon Apr 1, 2026
Just landed the automatically opened #2440
MikeMcC399 commentedon Apr 2, 2026
@nschonni
Good news that the cache caught up! It looks like it has a one hour cache refresh:
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 commentedon Apr 2, 2026