Closed andreeaflorescu closed 2 years ago
I think this one might actually need to be manually updated because I see that cargo is also configured. How often should the cargo related updates happen? Do we also want to do that weekly? CC: @alindima @petreeftime
I think this one might actually need to be manually updated because I see that cargo is also configured. How often should the cargo related updates happen? Do we also want to do that weekly? CC: @alindima @petreeftime
What does the cargo updates entail? This project doesn't have a Cargo.lock and I thought the rust version used for tests is set manually.
I don't think we need the cargo updates either. I think I added it by mistake when copy-pasting it from somewhere else
What does the cargo updates entail? This project doesn't have a Cargo.lock and I thought the rust version used for tests is set manually.
These updates are not related to Cargo.lock, and it does not matter if it's a lib crate or a bin crate. Having updates for dependencies is useful from time to time, and it depends on how you specify them in Cargo.toml. For example, if you specify dependencies with =v1.2.3
, then having a bot update them is useful because you can fix failures as a new version is released. You can decide for each dependency if you want to update it or not on a case by case basis, but with this method you are aware of the changes that are needed to move to a newer version.
This does not seem to be the case for this crate, so I will just convert this to a normal PR again.
This crate has very few PRs, so there is no reason to keep updating dependabot.