Compare commits

...

4 Commits

Author SHA1 Message Date
Karl Horky
99d917162a
Merge 9fe9d805a1 into a0853c2454 2025-09-03 17:57:31 -04:00
Karl Horky
9fe9d805a1
Clarify 2025-08-02 20:15:41 +02:00
Karl Horky
cadfbd215e
Make warning more apparent 2025-08-02 15:41:28 +02:00
Karl Horky
5db8d280d6
Add note about NVM and latest release syntax being outdated
Closes #1236 
Closes #1114
Closes #940

As extensively documented in #1236 and #940, the non-exact aliases `lts/*`, `*`, `current`, `latest`, and `22` are slow to be upgraded, lagging several days behind the Node.js releases.

Let users know about this downside.
2025-08-02 15:38:32 +02:00

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.