v1: CI: Fail if yarn.lock needs updates #2945
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.
This backports #2943 to the master branch.
This adds
--frozen-lockfile
to the yarn install to make it fail if the yarn.lock committed differs from what would be written after invoking yarn. This should prevent issues like those in #2942 and the one currently present in thev2
branchTest Plan: Let CI run with the first commit and let it fail. Add a commit fixing
yarn.lock
and let it pass.