René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Automation stuck on 26.6.0 >= 26.7.0 update","articleBody":"Run actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3\n22.23.2\n\n24.19.0\n\n26.6.0\n\nUpdating version 26...\n26/bookworm/Dockerfile is already up to date!\n26/bookworm-slim/Dockerfile is already up to date!\n26/bullseye/Dockerfile is already up to date!\n26/trixie/Dockerfile is already up to date!\n26/bullseye-slim/Dockerfile is already up to date!\n26/alpine3.23/Dockerfile is already up to date!\n26/trixie-slim/Dockerfile is already up to date!\n26/alpine3.24/Dockerfile is already up to date!\nDone!\n\nIt 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.\n\nIt looks like build-automation.mjs & update.sh need to be better coordinated.\n\n---\n\nI 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.\n\nThis 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\n\n\u003cimg width=\"283\" height=\"175\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/29a44100-55ac-4e88-9b32-208fb62fe8de\" />","author":{"url":"https://github.com/MikeMcC399","@type":"Person","name":"MikeMcC399"},"datePublished":"2026-08-05T18:38:56Z","url":"https://github.com/nodejs/docker-node/issues/2596"}