chore(nodejs): upgrade from 8 to 10 - EUBFR-263 #226
Merged
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
kalinchernev
added
tag: internal
and removed
process: review needed
tag: enhancement
labels
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.
PR description
Together with the version of Node.js, the rest of the dependencies have been upgraded as well with a few exceptions:
elasticsearch: if upgraded to next major, the following error appearsInvalid apiVersion "6.5", expected a function or one of _default, 7.0, 6.7, 5.6, 6.8, 7.1, 7.x, master@ecl/ec-preset-website: already done in feat(dashboards): initiate UI for consolidation work - EUBFR-248 #198 (it'd be better for feat(dashboards): initiate UI for consolidation work - EUBFR-248 #198 to go in first and then make the upgrade in this as there will be too many irrelevant changes to nodejs version)serverless: please see EUBFR-266Please keep in mind that
aws-sdkreceives at least a daily set of updates and there will always be a newer version between now and the time of making the review of the pull request.