ci(Dependabot): Distinguish major version bumps from minor/patch bumps - #917
Open
jessealama wants to merge 2 commits into
Open
jessealama wants to merge 2 commits into
jessealama wants to merge 2 commits into
Conversation
jessealama
requested review from
arademaker,
chenson2018,
fmontesi,
kim-em and
sorrachai
as code owners
September 17, 2026 09:07
jessealama
force-pushed
the
ci/dependabot-split-update-types
branch
from
September 17, 2026 11:21
90194b2 to
48ba8d7
Compare
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.
Follow-on to #895. Takes a more conservative approach to Dependabot updates by grouping bumps according to their semver impact rather than lumping everything together.
#912 is the motivating example. It's a single PR carrying three major version bumps (
actions/checkoutfrom v4 to v7,actions/github-scriptfrom v7 to v9, andsoftprops/action-gh-releasefrom v2 to v3) alongside ordinary minor/patch bumps. Mixing the two means the easy updates cannot be merged without also signing off on the major ones.Sometimes major version bumps might fail because they also need to be accompanied by minor/patch version bumps for other dependencies. But that's not a big deal. Manual intervention in such cases is always possible. (Of course, it's always possible that minor/patch bumps make the build go red and need manual intervention, too, but in theory that should be less likely.)
We also do the same here with the pip.