Potential race condition when starting unofficial-builds

[sxa]

Spotted during the v26.1.0 release:

• https://unofficial-builds.nodejs.org/logs/202605071005-v26.1.0/ has a repeating error in the retry loop of:

+ curl -fsSLO --compressed https://nodejs.org/download/release/v26.1.0/SHASUMS256.txt.asc
curl: (22) The requested URL returned error: 404
Curl failed with status 22. Retrying in 10 seconds...
+ echo 'Curl failed with status 22. Retrying in 10 seconds...'

Since the file it's trying to retrieve is now in place I suspect there is a race condition between when the unofficial builds gets triggered and the checksum file's signature appearing.

In this case the date stamp on the checksum file was 07-May-2026 10:07 and the log with the error was 07-May-2026 10:06. This should be analysed or a sleep put in between the retries to allow it to cope with a short delay in some of the required artefacts becoming available.

[nschonni]

I think the initial queue of the job is based off of the .tab file change if I'm understanding https://github.com/nodejs/unofficial-builds/blob/main/bin/check-releases.sh right.
It seems odd, but maybe the "wait" for the .asc should happen before the tarball downloads in

unofficial-builds/fetch-source/run.sh

Line 4 in 7159cd7

{