This repository has been archived by the owner on Nov 8, 2024. It is now read-only.
Use Node 12 in AppVeyor #1495
Merged
Use Node 12 in AppVeyor #1495
Conversation
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
|
Won't pass until #1494 is merged. |
honzajavorek
force-pushed
the
honzajavorek/fix-node-appveyor
branch
from
64a9c64 to
a84a2bb
Compare
artem-zakharchenko
approved these changes
Oct 1, 2019
|
🎉 This PR is included in version 12.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
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.
🚀 Why this change?
We always use the latest Node version we support when testing on AppVeyor. We added Node 12 to the other CI, but didn't switch AppVeyor to use it.
✅ What didn't I forget?
npm run lint