From 5db8d280d6d5783d384df6ad6144790cf32def8c Mon Sep 17 00:00:00 2001 From: Karl Horky Date: Sat, 2 Aug 2025 15:38:32 +0200 Subject: [PATCH] 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. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 92804e94..be65da64 100644 --- a/README.md +++ b/README.md @@ -123,7 +123,7 @@ Examples: - NVM LTS syntax: `lts/erbium`, `lts/fermium`, `lts/*`, `lts/-n` - Latest release: `*` 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. +**Note:** If you require timely version upgrades, use specific versions like `22.18.0` and upgrade the versions yourself. Values like `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 can be several days outdated. `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.