- Notifications
You must be signed in to change notification settings - Fork1.6k
Note non-exact versions syntax installing outdated versions#1335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Open
karlhorky wants to merge3 commits intoactions:mainChoose a base branch
base:main
Could not load branches
Branch not found:{{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
Closesactions#1236Closesactions#1114Closesactions#940As extensively documented inactions#1236 andactions#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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Pull Request Overview
Updates the README documentation to warn users about potential delays when using non-exact Node.js version aliases in GitHub Actions workflows.
- Adds a warning that non-exact version aliases (
lts/*,*,latest, etc.) can be several days outdated - Recommends using specific versions for timely upgrades
README.md Outdated
| -Latest release:`*`or `latest`/`current`/`node` | ||
| **Note:**Liketheother 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 upgradetheversions 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. |
CopilotAIAug 2, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
[nitpick] The sentence structure is overly complex and could be difficult to follow. Consider breaking this into separate sentences or restructuring for better readability.
Suggested change
| **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. | |
| **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). | |
| Which version you get depends on the[`check-latest`](docs/advanced-usage.md#check-latest-version) input. | |
| Both can be several days outdated. |
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
None yet
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes#1236
Closes#1114
Closes#940
Description:
As extensively documented in#1236 and#940, the non-exact aliases
lts/*,*,current,latest, and22are slow to be upgraded, lagging several days behind the Node.js releases.Let users know about this downside.
Related issue:
lts/*installs old LTS versions up to 1 month+ after release #1236lts/*installs old LTS version intermittently #940Check list: