Update merge-deep per SNYK-JS-MERGEDEEP-1070277 #3409
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.
Details
Update merge-deep to 3.0.3 to avoid a nasty vulnerability detailed in the snyk issue linked in this PR's GH issue. This is an update of a dependency, which is why the changes only appear in package-lock.json and not also in package.json.
Fixed Issues
Fixes https://github.com/Expensify/Expensify/issues/165494
Tests
Since
merge-deep
is an electron dependency, general regression testing of the desktop app should cover any issues that might arise from this change. I fired up the desktop app and the web app and carried on a conversation between two test users, look for anything that appeared out of the ordinary and did not encounter any.QA Steps
General regression testing of the desktop app should be sufficient.
Tested On