Conversation
Collaborator
Author
|
As usual, AppVeyor is a sloth for supporting new Node.js versions; I'll have to drop Node 16 tests on Windows for the time being. Yet another reason to switch to GH Actions. |
This was referenced Apr 29, 2021
JPeer264
approved these changes
Apr 29, 2021
Collaborator
JPeer264
left a comment
There was a problem hiding this comment.
Just for my understanding, is there actually a reason why we don't test node v15 on AppVeyor?
Collaborator
Author
|
@JPeer264 AppVeyor's performance generally isn't great, so we've traditionally only tested LTS releases there, to make the build run faster. GH Actions fixes this. |
Closed
78 tasks
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.
Not needed if we merge #881 and kill the old CI providers.Will need edits; still needenginesbump.