Repository navigation
latest & (current & node) install v27.0.0-alpha.0.0.0 not 26.13.0 #1660
Description
- follow-on from comment Provide
allow-prereleases(or similar) option for Node.js 27 Alpha #1657 (comment) - relates to
latestpoints to Alpha by version managers / nodejs.org points to LTS nodejs/node#67135
Description:
Selecting version latest causes Node.js 27.0.0-alpha.0.0.0 to be installed.
This is not the latest version as defined by the Node.js documentation Release types.
https://nodejs.org/download/release/latest/ contains builds for Node.js 26.13.0 which is the Active LTS version, and the highest non-alpha release.
Action version:
action/[email protected]
Platform:
- Ubuntu
- macOS
- Windows
Runner type:
- Hosted
- Self-hosted
Tools version:
N/A
Repro steps:
Specify node-version: latest
- name: Install Node.js latest
uses: actions/[email protected]
with:
node-version: latest
check-latest: trueSee setup-node-latest.yml for runnable reproduction.
Expected behavior:
Specifying latest should install Node.js 26.13.0 (or later from the same Node.js 26.x release line, when available).
Release types says:
The latest directory is an alias for the latest Current release.
Index of /download/release/latest/
../
docs/ - -
win-arm64/ - -
win-x64/ - -
SHASUMS256.txt.asc 28-Oct-2026 13:01 4.1 KB
SHASUMS256.txt.sig 28-Oct-2026 13:01 566 B
SHASUMS256.txt 28-Oct-2026 17:41 3.2 KB
node-v26.13.0-aix-ppc64.tar.gz 28-Oct-2026 12:59 83 MB
node-v26.13.0-arm64.msi 28-Oct-2026 12:59 33 MB
node-v26.13.0-darwin-arm64.tar.gz 28-Oct-2026 12:59 58 MB
node-v26.13.0-darwin-arm64.tar.xz 28-Oct-2026 12:59 31 MB
node-v26.13.0-darwin-x64.tar.gz 28-Oct-2026 12:59 60 MB
node-v26.13.0-darwin-x64.tar.xz 28-Oct-2026 12:59 33 MB
node-v26.13.0-headers.tar.gz 28-Oct-2026 12:59 10 MB
node-v26.13.0-headers.tar.xz 28-Oct-2026 12:59 584 KB
node-v26.13.0-linux-arm64.tar.gz 28-Oct-2026 12:59 63 MB
node-v26.13.0-linux-arm64.tar.xz 28-Oct-2026 12:59 33 MB
node-v26.13.0-linux-ppc64le.tar.gz 28-Oct-2026 12:59 65 MB
node-v26.13.0-linux-ppc64le.tar.xz 28-Oct-2026 12:59 33 MB
node-v26.13.0-linux-s390x.tar.gz 28-Oct-2026 12:59 65 MB
node-v26.13.0-linux-s390x.tar.xz 28-Oct-2026 12:59 33 MB
node-v26.13.0-linux-x64-musl.tar.gz 28-Oct-2026 12:59 63 MB
node-v26.13.0-linux-x64-musl.tar.xz 28-Oct-2026 12:59 34 MB
node-v26.13.0-linux-x64.tar.gz 28-Oct-2026 12:59 63 MB
node-v26.13.0-linux-x64.tar.xz 28-Oct-2026 12:59 34 MB
node-v26.13.0-win-arm64.7z 28-Oct-2026 12:59 24 MB
node-v26.13.0-win-arm64.zip 28-Oct-2026 12:59 37 MB
node-v26.13.0-win-x64.7z 28-Oct-2026 12:59 26 MB
node-v26.13.0-win-x64.zip 28-Oct-2026 12:59 41 MB
node-v26.13.0-x64.msi 28-Oct-2026 12:59 37 MB
node-v26.13.0.pkg 28-Oct-2026 12:59 105 MB
node-v26.13.0.tar.gz 28-Oct-2026 12:59 127 MB
node-v26.13.0.tar.xz 28-Oct-2026 12:59 63 MBActual behavior:
actions/setup-node installs v27.0.0-alpha.0.0.0 when asked for latest
Run actions/[email protected]
with:
node-version: latest
check-latest: true
token: ***
package-manager-cache: true
getting latest node version...
getting latest node version...
Attempt to resolve the latest version from manifest...
Failed to resolve version v27.0.0-alpha.0.0.0 from manifest
Attempting to download v27.0.0-alpha.0.0.0...
Not found in manifest. Falling back to download directly from Node
Acquiring 27.0.0-alpha.0.0.0 - x64 from https://nodejs.org/dist/v27.0.0-alpha.0.0.0/node-v27.0.0-alpha.0.0.0-linux-x64.tar.gz
Extracting ...
/usr/bin/tar xz --strip 1 --warning=no-unknown-keyword --overwrite -C /home/runner/work/_temp/aa316193-6949-4603-bec6-c73e4bd2ceb6 -f /home/runner/work/_temp/57b2047f-1960-4aad-a93d-830eee1e5900
Adding to the cache ...
Done
Environment details
node: v27.0.0-alpha.0.0.0
npm: 12.1.0
yarn: 1.22.22
Activity
MikeMcC399 commentedon Nov 3, 2026
Workaround
It appears that specifying '*' will install the latest non-prerelease version of Node.js according to SemVer syntax rules. At the moment, this is Node.js 26.13.0, the Active LTS release.
node-versionaliasv-gowridurgad commentedon Nov 3, 2026
Hi @MikeMcC399 , thanks for the report. Currently in
actions/setup-node,latest,currentandnoderesolve to the latest dist version, which includes prereleases. We'll align them with nodejs.org so they resolve to the newest stable release, and we'll share an update once the change is released.MikeMcC399 commentedon Nov 3, 2026
Thank you very much @v-gowridurgad !
I also raised an issue nodejs/node#67224 regarding the documentation.
Although the intention for the definition of
latestwas always to mean the highest non-prerelease version, the description has become confused and needs to be clarified.For
actions/setup-nodeit's important that users don't accidently get a pre-release Alpha version, if they expected to get a latest stable release.If you could also define an alias that installs the latest version including pre-release alpha versions, that would be awesome, but it's actually more a topic for the feature request #1657.
[-]`latest` installs v27.0.0-alpha.0.0.0 not 26.13.0[/-][+]`latest` & (`current` & `node`) install v27.0.0-alpha.0.0.0 not 26.13.0[/+]v-gowridurgad commentedon Nov 13, 2026
Hi everyone, We have raised PR #1668 to address this issue.
With this change, the latest, current, and node aliases will resolve to the latest stable Node.js release, excluding prereleases.
Any feedback or suggestions would be greatly appreciated. Thanks in advance!