Release artifacts for 18.19.0 Alpine builds are missing

[knksmith57]

What is the expected behavior? Why is that the expected behavior?

18.19.0 artifacts for Alpine should be available here: https://unofficial-builds.nodejs.org/download/release/v18.19.0/. They are not.

What do you see instead?

❯ curl -I https://unofficial-builds.nodejs.org/download/release/v18.19.0/SHASUMS256.txt
HTTP/1.1 404 Not Found
Server: nginx
Date: Fri, 01 Dec 2023 17:06:50 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive

Additional information

See nodejs/docker-node#2002

[knksmith57]

I'm unfamiliar with how to help diagnose but suspect whatever release job handles the artifact uploads for Alpine variants either failed to generate or upload all artifacts for the 18.19.0 release to: https://unofficial-builds.nodejs.org/download/release/v18.19.0/

[knksmith57]

Found the build log: https://unofficial-builds.nodejs.org/logs/202311291715-v18.19.0/fetch-source.log

Looks like there might be some sort of race condition in the unofficial builds CI. I see the SHASUMS256.txt.asc file it attempted (and failed) to fetch returned a 404, but that artifact is now returning a 200 for me: https://nodejs.org/download/release/v18.19.0/SHASUMS256.txt.asc

The docs on how the release builds are triggered is here: https://github.com/nodejs/unofficial-builds#how, but I'm not sure there's a way for me to provide any additional help. It sounds like someone with access needs to kick/re-queue the unofficial release build.

[richardlau]

According to https://unofficial-builds.nodejs.org/logs/202311291715-v18.19.0/ the sources failed to download.
I've queued a rebuild.
Update: building. Logs: https://unofficial-builds.nodejs.org/logs/202312011733-v18.19.0/

[knksmith57]

Awesome, thank you 🙏

[knksmith57]

Artifacts look good! Thank you, @richardlau!