Manage Node.js version using .node-version file #1224
Merged
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.
Manage Node.js version using .node-version file
Goal
Ensure the Node.js version is consistent across different environments by using a
.node-versionfile.How
actions/setup-nodein the GitHub Actions workflows..node-versionfile in the root of your repository.actions/setup-nodestep in your GitHub Actions workflows to read the.node-versionfile.Example
Before:
After:
Acceptance Criteria
.node-versionfile is created in the root of the repository with the correct Node.js version.actions/setup-nodesteps in GitHub Actions workflows are usingnode-version-fileinput.actions/setup-nodesteps in GitHub Actions workflows are not usingnode-versioninput.