Split cargo group into cargo-minor and cargo-patch #2719
Merged
Conversation
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
|
Thats a great idea! |
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.
The most recent Dependabot PR, #2717, has run into a few issues some of which I was able to solve, some of which I wasn’t.
The issues currently preventing the PR from being green are related to
cargo denynot allowing duplicate versions of dependencies.This PR is an attempt at mitigating the impact of this issue. It splits the
cargogroup into 2 groups,cargo-minorandcargo-patch. My hope is that thecargo-patchgroup will more often be green without human intervention, thus enabling us to fast-track merging patch updates.The
cargo-minorgroup, on the other hand, will become smaller, thus making it easier for us to review and potentially handle updates by hand.What do you think?