chore: prevent unintended changes to lock files#40037
chore: prevent unintended changes to lock files#40037
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
|
Looks like this PR is not ready to merge, because of the following issues:
Please fix the issues and try again If you have any trouble, please check the PR guidelines |
0960e00 to
a5a055d
Compare
Proposed changes (including videos or screenshots)
We're changing CI scripts and Dockerfiles to break if there is a change to the monorepo's lock file. This prevents us from adding dependencies manually without committing
yarn.lockitself.Issue(s)
Steps to test or reproduce
Further comments