Repository navigation
ci: let Dependabot label all its pull requests - #493
Conversation
Remove `target-branch` from every Dependabot entry: it names the default branch anyway, and while it is set, GitHub doesn't apply an entry's options, labels included, to security updates. Security update pull requests then get `type: dependencies` instead of Dependabot's own labels. The `ignore` rules now also apply to security updates, as intended. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reviewer's GuideConfigurationRemove
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dev #493 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 35 35
Lines 3239 3239
=========================================
Hits 3239 3239 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Linked issuesChecked at commit eea5568 #492 ci: let Dependabot label all its pull requests · 5 of 6 met · 1 to check by hand
|
There was a problem hiding this comment.
Hey - I've reviewed your changes and they look great!
Sourcery assessment
Needs a human reviewer. With target-branch removed, Dependabot’s existing ignore rules can now suppress matching security-update PRs, leaving affected dependencies without an offered fix. Reverting restores the prior behavior, but any time spent running with an update suppressed cannot be undone.
Summary
Lets Dependabot label all its pull requests, security updates included, with the organisation's label
type: dependenciesonly, instead of its own labels (dependenciesplus an ecosystem label).In
.github/dependabot.yml:target-branch: devfrom the 4 entries that set it (uv, github-actions, docker, pre-commit) and from the multi-ecosystem groupservice-images.devis the default branch, so version updates still target it.target-branchwith one that explains why no entry sets it.ignorerules. They now also apply to security updates: theconnexionmajor hold, the MongoDB 7.0 hold,foca-common(bumped by hand), andfocaandelixircloud/foca, which are bumped by hand together with the base image (a lone bump breaks the image build), so Dependabot won't open security updates for FOCA either. That's intended.Nothing else changes: compared as data (keys sorted), the new file equals the old one minus
target-branchpluslabelson every entry.Closes #492
Light lane: CI configuration only (Dependabot), no secrets, permissions or release workflow touched, so the reviewer subagents were skipped; I reviewed the diff myself.
Verification
yqparses the new.github/dependabot.yml; everyupdatesentry haslabels: ["type: dependencies"]; notarget-branchis left.yq -o=json 'sort_keys(..)'): only the intended change.CI passedgreen) after mergingdev, which brought the dnspython fix of build(deps): bump dnspython from 2.9.1 to 2.9.2 #491 (CVE-2026-128089 had failedScan imagebefore).Declined review findings
None.
Open questions
None.
🤖 Generated with Claude Code
Summary by Sourcery
Enhancements:
type: dependencieslabel consistently to all pull requests, including security updates, by relying on the default branch rather than explicit target branches.