Build Tools: Update actions/setup-node GitHub action#40816
Merged
Conversation
|
Size Change: 0 B Total Size: 1.23 MB ℹ️ View Unchanged
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What?
Follow-up for changes in WordPress core applied by @desrosj with WordPress/wordpress-develop@567b837.
This PR updates
actions/setup-nodeGitHub action from2.4.1to3.1.0.Additionally, this updates nearly all instances of the
actions/setup-nodeaction to replace thenode-versionoption with the newnode-version-file. This simplifies the process of changing the version of NodeJS used in workflows by only requiring the version to be changed once in the.nvmrcfile. We only exclude places where wematrixis used more than one version of Node.js or to use it also for caching.Why?
To have the most recent version and to align with WordPress core.
How?
An update for workflows that use
actions/setup-nodeaction.Testing Instructions
All CI jobs should still pass and use Node.js 14.