-
Notifications
You must be signed in to change notification settings - Fork 595
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
Cargo.lock: update semver compatible deps #1874
Conversation
So why aren't we updating to base64 0.22? |
You want to see the |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1874 +/- ##
=======================================
Coverage 95.47% 95.47%
=======================================
Files 85 85
Lines 18589 18589
=======================================
Hits 17747 17747
Misses 842 842 ☔ View full report in Codecov by Sentry. |
I would expect a change to update |
Added a separate commit for the I'll make sure to include these dev dep updates as part of the regular process for future PRs. |
Though, now that we know the upstream dependabot folks aren't likely to make their automation work the way we want I'm perhaps more open to the idea of using renovatebot like @ctz suggested at one point. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW, I also think having one commit per semver-compatible dep isn't really worth it.
For Renovate, the rustup repo has a decent setup which we could steal from.
Benchmark resultsInstruction countsSignificant differencesThere are no significant instruction count differences Other differencesClick to expand
Wall-timeSignificant differencesThere are no significant wall-time differences Other differencesClick to expand
Additional informationCheckout details:
|
Replaces #1871