It would be good if you could specify in the config.yml that you want minor, patch and security updates but not major version change updates. Is this possible now or going to be possible?
Assuming that you have a high test coverage, you can use auto-merging and opt out for major version upgrades:
automerged_updates:
- match:
dependency_type: all
update_type: semver:minor
Thus, you will still get the major upgrade PRs, but only minors and patches are auto-merged.
+1 it would be good to in the config file either allow only patch/minor updates or ignore major versions. Is there something is being looked at in v2, since there is no update since March?
This is similar to #2154 and #2219 as well. There's seems to be a demand for limiting the scope of a update to a version group or level. I would be interested in two different managers running on different schedules to handle patch/minor/major with different frequency. I can envision different strategies that approach with opposite frequencies, for example:
update_type: "semver:patch" would be very helpful here.
Being able to filter by version types would also allow for labelling them differently - opening up lots of possibilities with GitHub actions.
e.g.
updates:
- package-ecosystem: npm
update_types:
- "semver:patch"
- "semver:minor"
labels:
- "dependency"
- "automerge"
- package-ecosystem: npm
update_types:
- "semver:major"
labels:
- "dependency"
and then automerge any PRs with the automerge label.
Duplicate of https://github.com/dependabot/dependabot-core/issues/2219 ?
Most helpful comment
Being able to filter by version types would also allow for labelling them differently - opening up lots of possibilities with GitHub actions.
e.g.
and then automerge any PRs with the
automergelabel.