This repository has been archived by the owner on Jul 24, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Workaround waiting for AppVeyor to add Node versions
- Loading branch information
Showing
1 changed file
with
4 additions
and
2 deletions.
There are no files selected for viewing
This file contains 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
12c0052
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.
@xzyfer @nschonni: just a reminder that this should be reverted when AppVeyor has Node.js 12. Because if not, when Node.js 13 is out it'll use that.
12c0052
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.
Is that true? What's the point of the node_version substitution?
12c0052
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.
Oops, didn't see you had added the environment variable in another commit.
All good then, but still I'd personally just remove this when Node.js 12 is added on AppVeyor, but maybe that's only me . I mean on the other hand this ensures you are always getting the latest Node.js release of the specified versions, so it's good that way.