-
-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: assert yarn prints no warnings #5565
Conversation
Performance Report✔️ no performance regression detected Full benchmark results
|
Looks good but the job succeeds either way are we fine with this behavior for now? I am not sure we can fix all warnings, most of unmet peer dep warnings were resolved here |
Hmm the script should not succeed actually, there are warnings now. Does yarn emit warnings via stdout or stderr? |
This is the output of the job
The script works but we are still exiting with code 0. Probably just have to do |
Oh lol, forgot that line |
🎉 This PR is included in v1.10.0 🎉 |
Motivation
Description
yarn does not offer a clean way to trigger those warnings. From yarnpkg/yarn#4594 and some local tests --check-files seem to work fine, but I haven't tested on CI before opening this PR
Closes #5115