Sync yarn.lock with recent changes to package.json
What does this MR do?
two MRs got merged into master with package.json changes around the same time yarn got merged in. Because of this yarn.lock doesn't contain entries that were added to package.json which will cause CI to fail.
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master(if it does - rebase it please) -
Squashed related commits together