René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`automatic-updates` waited for `musl` builds","articleBody":"Follows on from https://github.com/nodejs/docker-node/issues/2539\n\n## Current behavior\n\n[automatic-updates.yml](https://github.com/nodejs/docker-node/actions/workflows/automatic-updates.yml) did not create a PR for the June 18, 2026 security release until all `musl` builds were available.\n\nThe PR https://github.com/nodejs/docker-node/pull/2540 was created June 18, 2026 06:56 UTC and only after \nhttps://unofficial-builds.nodejs.org/download/release/v22.23.0/node-v22.23.0-linux-arm64-musl.tar.xz was completed at 18-Jun-2026 06:28 (UTC).\n\n## Expected behavior\n\nFor security releases, as described in [README \u003e Release Availability](https://github.com/nodejs/docker-node#release-availability), it is expected that Debian releases may be published without Alpine releases if the `musl` builds are not available.\n\nIf any `musl` builds are missing, this should not prevent [automatic-updates.yml](https://github.com/nodejs/docker-node/actions/workflows/automatic-updates.yml) creating a PR for Debian releases.\n\nFor the situation where some but not all `musl` builds are missing, then the Alpine releases for which the `musl` builds are available should be processed and a PR created. (This situation is currently not documented or described anywhere.)\n\n## Logs\n\nhttps://github.com/nodejs/docker-node/actions/runs/27739246196 executed at Thu, 18 Jun 2026 05:40:31 GMT showed:\n\n    Run actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3\n    22.22.3\n\n    24.16.0\n\n    26.3.0\n\n    There's no musl build for version 22.23.0 yet.\n\nso although this is a security release, which is supposed to bypass the need for `musl` builds, no PR is being created.\n\nhttps://github.com/nodejs/docker-node/actions/runs/27742307859 executed at Thu, 18 Jun 2026 06:56:02 GMT showed:\n\n    Run actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3\n    22.22.3\n\n    24.16.0\n\n    26.3.0\n\n    Updating version 22...\n    22/bookworm/Dockerfile updated!\n    22/bookworm-slim/Dockerfile updated!\n    22/bullseye/Dockerfile updated!\n    22/trixie/Dockerfile updated!\n    22/alpine3.23/Dockerfile updated!\n    22/bullseye-slim/Dockerfile updated!\n    22/alpine3.24/Dockerfile updated!\n    22/trixie-slim/Dockerfile updated!\n    Done!\n\n    Updating version 24...\n    24/bookworm/Dockerfile updated!\n    24/bookworm-slim/Dockerfile updated!\n    24/alpine3.23/Dockerfile updated!\n    24/alpine3.24/Dockerfile updated!\n    24/bullseye/Dockerfile updated!\n    24/bullseye-slim/Dockerfile updated!\n    24/trixie/Dockerfile updated!\n    24/trixie-slim/Dockerfile updated!\n    Done!\n\n    Updating version 26...\n    26/bookworm/Dockerfile updated!\n    26/bookworm-slim/Dockerfile updated!\n    26/bullseye/Dockerfile updated!\n    26/bullseye-slim/Dockerfile updated!\n    26/trixie-slim/Dockerfile updated!\n    26/trixie/Dockerfile updated!\n    26/alpine3.23/Dockerfile updated!\n    26/alpine3.24/Dockerfile updated!\n    Done!\n\n## Note\n\nNote that the situation recovered on its own. This issue is just described here to present an opportunity for improving the workflow for future security releases.","author":{"url":"https://github.com/MikeMcC399","@type":"Person","name":"MikeMcC399"},"datePublished":"2026-06-18T09:27:13.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/2541/docker-node/issues/2541"}