Skip to content

feat: group Dependabot security updates and cancel superseded PR runs in the templates - #8

Merged
rubenhensen merged 2 commits into
mainfrom
rhensen/yiv-401-security-groups-concurrency
Oct 27, 2026
Merged

rubenhensen merged 2 commits into
mainfrom
rhensen/yiv-401-security-groups-concurrency

Conversation

@rubenhensen

Copy link
Copy Markdown
Contributor

Two changes to the templates, after the first Dependabot run in the migrated repositories:

  • templates/dependabot.yml: the groups only applied to version updates, so every security update came as its own PR. vcmrtd got 15 of them on one evening. A group with applies-to: security-updates per ecosystem (actions, go, npm) bundles them. Docker and Terraform have no advisories, so they get no such group. This repository's own dependabot.yml gets the same group.
  • Caller templates (status-checks-go, status-checks-node, terraform): workflow-level concurrency keyed on the PR number with cancel-in-progress. A new push now cancels the PR's previous run, including the Docker builds and the caller's own jobs, which the job-level groups in the reusable workflows don't cover. Push, schedule and merge-queue runs get run_id as their group, so they never wait or cancel. That matters for Terraform apply on main. The job-level groups have different names, so there is no deadlock.

The same change goes to the 75 repositories that already use the shared workflows (YIV-401).

This was referenced Oct 27, 2026
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