Repository navigation
Automatically merge dependabot PRs - #4211
Merged
djmitche merged 2 commits intoOct 20, 2026
Merged
Conversation
Collaborator
|
I'm not sure it's strictly related but have you considered batching dependabot updates? (I presume there's an easy way to do that.) The main point of committing Cargo.toml and updating it regularly is that CI detects breakages, right? My thought is that at a certain point the ratio of PR's to breakages detected might be more noise than it's worth. |
Member
Author
|
They are batched, but currently daily. I will change that to weekly. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm doing this with my fingers anyway -- it's been a long time since I've looked carefully at upstream commits or anything like that. We have a cooldown configured for dependabot, and anyway we're not deploying on commit, so there's plenty of time for a compromised upstream to get discovered (by someone else) and yanked.