actions/setup-node
1
0
Fork 0
mirror of https://github.com/actions/setup-node.git synced 2025-08-12 11:32:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge 9fe9d805a10a7669a61e69d7c25183dbe1ef0ab2 into 5e2628c959b9ade56971c0afcebbe5332d44b398

Browse Source
This commit is contained in:
Karl Horky 2025-08-02 18:15:44 +00:00 committed by GitHub
commit 9805dbb579
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -118,12 +118,12 @@ The `node-version` input supports the Semantic Versioning Specification, for mor
Examples:
- Major versions: `18`, `20`
- More specific versions: `10.15`, `16.15.1` , `18.4.0`
- NVM LTS syntax: `lts/erbium`, `lts/fermium`, `lts/*`, `lts/-n`
- Latest release: `*` or `latest`/`current`/`node`
- Specific versions: `10.15`, `16.15.1` , `18.4.0`
- Major versions (see Caveat below): `18`, `20`
- NVM LTS syntax (see Caveat below): `lts/erbium`, `lts/fermium`, `lts/*`, `lts/-n`
- Latest release (see Caveat below): `*` or `latest`/`current`/`node`
**Note:** Like the other values, `*` will get the latest [locally-cached Node.js version](https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md#nodejs), or the latest version from [actions/node-versions](https://github.com/actions/node-versions/blob/main/versions-manifest.json), depending on the [`check-latest`](docs/advanced-usage.md#check-latest-version) input.
**Caveat:** If you require timely version upgrades, use specific versions like `22.18.0` and upgrade the versions yourself. Non-specific versions like `22`, `lts/*`, `*`, `latest`, etc. will get the latest [locally-cached Node.js version](https://github.com/actions/runner-images/blob/main/images/ubuntu/Ubuntu2204-Readme.md#nodejs), or the latest version from [actions/node-versions](https://github.com/actions/node-versions/blob/main/versions-manifest.json), depending on the [`check-latest`](docs/advanced-usage.md#check-latest-version) input. Both of these sources can be slow to upgrade, with multiple days or weeks of lag time after the version release.
`current`/`latest`/`node` always resolve to the latest [dist version](https://nodejs.org/dist/index.json).
That version is then downloaded from actions/node-versions if possible, or directly from Node.js if not.