Repository navigation
v27 nightly releases missing from https://nodejs.org/download/nightly/ directory #1018
Description
I can't find any releases with v27.0.0* in the directory https://nodejs.org/download/nightly/
The last previously listed nightly is:
https://nodejs.org/download/nightly/v26.0.0-nightly20260417b178842482/ from Apr 2026
https://nodejs.org/download/nightly/index.json on the other hand shows:
[
{
"version": "v27.0.0-nightly202609067aba44d4ac",
"date": "2026-09-06",
"files": [
"aix-ppc64",
"headers",
"linux-ppc64le",
"linux-s390x",
"linux-x64",
"linux-x64-musl",
"osx-arm64-tar",
"osx-x64-pkg",
"osx-x64-tar",
"src",
"win-arm64-7z",
"win-arm64-zip",
"win-x64-7z",
"win-x64-exe",
"win-x64-msi",
"win-x64-zip"
],
"npm": "11.19.1",
"v8": "14.6.202.34",
"uv": "1.52.1",
"zlib": "1.3.2.1-motley",
"openssl": "3.5.8",
"modules": "147",
"lts": false,
"security": false
},but
curl -I https://nodejs.org/download/nightly/v27.0.0-nightly202609067aba44d4ac/produces only HTTP/2 404.
Activity
targos commentedon Sep 7, 2026
They are on the origin server: https://direct.nodejs.org/download/nightly/
MikeMcC399 commentedon Sep 7, 2026
@targos
Are you able to pinpoint why they're not getting promoted to https://nodejs.org/download/nightly/ or does this need help from @nodejs/web-infra ?
ovflowd commentedon Sep 7, 2026
Only closest issue I see is #1006
ovflowd commentedon Sep 7, 2026
I forwarded this to the team, btw
richardlau commentedon Sep 7, 2026
AFAICT the nightlies are in both the staging and production R2 buckets, e.g.
araujogui commentedon Sep 7, 2026
Had a look at this. Only the directory listings are broken; the files themselves are in R2 and download fine:
So it's a worker bug, not anything on the build or upload side.
Since #1002, prod has served the nightly/, rc/, v8-canary/, test/ and docs/ listings out of a KV cache, and nothing refreshes it. The rebuild is manual only, and it last ran on 2026-04-17 and failed. That's also where the working nightlies stop. On a cache miss the worker just 404s instead of falling back to listing the bucket.
Re-running Build Directory Cache workflow should fix the issue. Longer term it probably needs a scheduled refresh, and a cache miss should fall back to the bucket rather than 404ing.
richardlau commentedon Sep 7, 2026
I'm going to move this to https://github.com/nodejs/release-cloudflare-worker as it sounds like the issue is there.
ci: update directory cache nightly