Automation stuck on 26.6.0 >= 26.7.0 update

[MikeMcC399]

Run actions/github-script@3a2844b
22.23.2

24.19.0

26.6.0

Updating version 26...
26/bookworm/Dockerfile is already up to date!
26/bookworm-slim/Dockerfile is already up to date!
26/bullseye/Dockerfile is already up to date!
26/trixie/Dockerfile is already up to date!
26/bullseye-slim/Dockerfile is already up to date!
26/alpine3.23/Dockerfile is already up to date!
26/trixie-slim/Dockerfile is already up to date!
26/alpine3.24/Dockerfile is already up to date!
Done!

It has recognized that there is a new version available, however it seems to be getting its data from different cached Cloudflare servers which are out of sync.

It looks like build-automation.mjs & update.sh need to be better coordinated.

---

I imagine that it will sort itself out if left alone when the caches catch up with each other. It shouldn't be like this though. Node.js version managers already pick up 26.7.0 as the latest 26.x release.

This is what GitHub Actions is seeing as the directory listing of https://nodejs.org/dist and it is missing the entry for v26.7.0

[MikeMcC399]

So, as expected, the directory listing of https://nodejs.org/dist got refreshed, and the workflow automatically created a PR #2597 which has been merged. https://hub.docker.com/_/node also now includes Node.js 26.7.0 images.

The immediate incident has resolved itself.

The underlying problem remains.

[MikeMcC399]

docker-node/update.sh

Line 118 in da57e74

fullVersion="$(curl -sSL --compressed "${baseuri}" | grep '<a href="v'"${version}." | sed -E 's!.*<a href="v([^"/]+)/?".*!\1!' | cut -d'.' -f2,3 | sort -V | tail -1)"

causes an issue because it is scraping the directory listing of baseuri https://nodejs.org/dist and this may not have refreshed to be in sync with https://nodejs.org/download/release/index.json

It would be preferable if only https://nodejs.org/download/release/index.json were used as a source of version availability and status.

It's also inconsistent to have an environment variable baseuri defined, and then for

docker-node/build-automation.mjs

Lines 36 to 38 in da57e74

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

to hardcode where it gets its information

If https://nodejs.org/download/release/index.json indicates that a certain version is supposed to be available, and artifacts at https://nodejs.org/dist/v$NODE_VERSION are missing (or the whole directory is missing), then this should be logged as an error.

[MikeMcC399]

This is actually a duplicate of the unresolved issue described in #2514. So I will join @nschonni in duplicating one of my own issues! 😉