vet: add dependency checks#7766
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #7766 +/- ##
==========================================
+ Coverage 80.25% 81.24% +0.99%
==========================================
Files 367 368 +1
Lines 36622 36779 +157
==========================================
+ Hits 29391 29882 +491
+ Misses 6043 5653 -390
- Partials 1188 1244 +56 |
easwars
left a comment
There was a problem hiding this comment.
I'm fine with the approach here.
Maybe:
- we just need to make enough noise for code authors and reviewers to be mindful of changes to dependencies
- put the instructions to regenerate deps somewhere accessible (for new folks on the team and for external contributors so that reviewers can point to it easily)?
I added an error message in vet and also made a separate script for generating. PTAL! |
easwars
left a comment
There was a problem hiding this comment.
Thanks for making the changes.
5eab4c2 to
ac76cff
Compare
fe6f52f to
6f9ac3d
Compare
|
Added a new workflow for this instead that turns red when deps change in any way. Here's what it looks like when there is a failure: And here's a pass from this PR: I had to temporarily copy the |
|
We also need a new PR description since we have a new approach now. |
Fixes #7690
This change adds a new GA workflow to compare dependencies before and after a PR. If they change, it will report a red X. We will not require this check to pass for merging, but it should be inspected to see if the change in dependencies is reasonable and expected.
RELEASE NOTES: none