feat: Use node v10 #158
Merged
feat: Use node v10 #158
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
_Potentially breaking release_, so tagged as a feature in case users need to pin to an older version rather than update unmaintained node
djones
pushed a commit
that referenced
this pull request
Feb 3, 2020
# [1.1.0](v1.0.8...v1.1.0) (2020-02-03) ### Features * Use node v10 ([#158](#158)) ([b70fa71](b70fa71))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Potentially breaking release, so tagged as a feature in case users need to pin to an older version rather than update unmaintained node
We don't specify node-engines in this package, so there is technically no change in the next release since this is only a CI config change. But better safe than sorry.