breaking: drops Node v14 & upgrades to Node v16 #286
Closed
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
|
@Pixelik could you please rework a bit the PR description to mark this "breaking change" 🙏 It's not just that you updated the CI to Node 16, you also dropped the support for Node 14, so consumer app could break. |
|
Done 👍 ❤️ |
Pixelik
changed the title
|
This PR will be replaced by #305 which does a complete global upgrade. |
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.
Breaking
Drops support for
Node v14(#286)Chore
Updates to
Node v16(#286)Updates to
eslint-plugin-qunit v8(which requires Node >=16) (#286)