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
build: bump bazel to 4.2.1 #64455
build: bump bazel to 4.2.1 #64455
Conversation
|
Job | Step | Action |
---|---|---|
Run mypy |
This comment was automatically generated by Dr. CI (expand for details).
Follow this link to opt-out of these comments for your Pull Requests.Please report bugs/suggestions to the (internal) Dr. CI Users group.
Codecov Report
@@ Coverage Diff @@
## master #64455 +/- ##
==========================================
+ Coverage 66.71% 66.79% +0.07%
==========================================
Files 708 708
Lines 92330 92330
==========================================
+ Hits 61596 61668 +72
+ Misses 30734 30662 -72 |
Should be good to |
Looks good to mind, but do you mind explaining what's the motivation behind the change?
@malfet has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
TBH, just to keep the build up to date (also trying to find out if bazel has some issue with the latest release or not) This is just a build config change, it should be technically trivial to update whenever there is a new release. What do you think? |
No description provided.
The text was updated successfully, but these errors were encountered: