Update dependencies to remove vulnerabilities #610
Merged
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.
Description and Context
Updating dependencies to remove vulnerabilities as referenced in #593
6.5.1
->7.32.0
(7.0.0 release notes)8.3.0
(8.0.0 release notes) because it requires node >= 12, and we currently only require node >= 10, so this requires more thought6.3.1
->8.2.0
(7.0.0 release notes, 8.0.0 release notes)3.0.1
->5.1.0
(4.0.0 release notes, 5.0.0 release notes)4.1.0
->4.1.2
5.0.0
(release notes) because it requires node >= 12, and we currently only require node >= 10, so this requires more thoughtspinnies contains a vulnerability that was added since
0.3.2
(current version is0.5.1
). Since we rely on some functionality that has been added, we will leave this version for now and see if we can get a PR to fix the issue in the spinnies repo.Lerna contains most of the remaining vulnerabilities, but has not been updated since
4.0.0
, which we are using. There is an issue to update the dependencies to remove vulnerabilities, which is promising.Screenshots
Output of

yarn audit
before this PROutput of

yarn audit
after this PRTODO
Who to Notify
@arinker @gcorne @brandenrodgers @kemmerle