Closed
Conversation
Contributor
|
👋 Hey @Andarist, Right now Node 14 isn't an option for actions. The Node 12 binary is shipped with the Actions Runner, so that will need to be updated before we can specify newer version of Node. The tracking issue for that is actions/runner#772. If you want to execute a Node 14 or higher script in your workflow, I'd recommend manually doing that with a |
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
2 participants
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.
It would be nice to upgrade the node version as it's the current LTS - I got bitten by this because my script has failed on unexpected syntax as I've used the optional chaining operator in it 😅