Skip to content

ci(dependabot): group cargo and github-actions updates into one PR each - #471

Open
ebourgeois wants to merge 1 commit into
mainfrom
chore/dependabot-groups
Open

ci(dependabot): group cargo and github-actions updates into one PR each#471
ebourgeois wants to merge 1 commit into
mainfrom
chore/dependabot-groups

Conversation

@ebourgeois

Copy link
Copy Markdown
Contributor

Why

The main ruleset requires up-to-date branches with linear history: every merge marks all other open PRs BEHIND, forcing a rebase + full ~20-min CI cycle per PR. Five separate github-actions PRs (#460, #462#465) recently cost five serialized CI runs, and any unrelated merge reset the whole chain.

What changes

  • cargo: the rust-dependencies catch-all group now includes majors. Dependabot opens at most two weekly cargo PRs: kube-ecosystem (unchanged — kube/k8s-openapi/kube-lease-manager are version-coupled and must move as a unit) + everything else.
  • github-actions: new catch-all group covering all update types → one weekly PR for all action bumps.

Behavior note

A major bump inside a grouped PR makes the whole PR report version-update:semver-major, so the dependabot auto-merge workflow holds it for manual review — the fail-safe behavior is unchanged. No effect on already-open PRs beyond dependabot rebasing them into the new grouping on its next run.

The main ruleset requires up-to-date branches with linear history, so
every merge marks all other open PRs BEHIND and forces a rebase plus a
full ~20-minute CI cycle per PR. Five separate github-actions PRs
recently cost five serialized CI runs.

- cargo: extend the rust-dependencies catch-all group to majors (the
  kube-ecosystem group stays separate and first, since kube/k8s-openapi/
  kube-lease-manager must move as a unit)
- github-actions: add a catch-all group covering all update types

Dependabot now opens at most one weekly PR per ecosystem (two for cargo:
kube-ecosystem + everything else). Note: a major bump inside a group
makes the whole grouped PR report as major, so the auto-merge workflow
holds it for manual review — the fail-safe behavior is unchanged.

Signed-off-by: Erick Bourgeois <erick@jeb.ca>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant