[uniqueg]

Summary

Lets Dependabot label all its pull requests, security updates included, with the organisation's label type: dependencies only, instead of its own labels (dependencies plus an ecosystem label).

In .github/dependabot.yml:

• Add labels: ["type: dependencies"] to every updates entry (3: uv, github-actions, pre-commit).
• Remove target-branch: dev from every entry (3 entries). dev is the default branch, so version updates still target it.
• Replace the header comment about target-branch with one that explains why no entry sets it.
• There are no ignore rules, so security updates change only in their labels.

Nothing else changes: compared as data (keys sorted), the new file equals the old one minus target-branch plus labels on every entry.

Closes #300

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

• yq parses the new .github/dependabot.yml; every updates entry has labels: ["type: dependencies"]; no target-branch is left.
• Semantic diff against the default branch (yq -o=json 'sort_keys(..)'): only the intended change.
• CI: all checks pass (CI passed green).

Declined review findings

None.

Open questions

None.

🤖 Generated with Claude Code

Summary by Sourcery

Standardize Dependabot pull request labeling while relying on the repository’s default branch configuration.

Enhancements:

• Configure all Dependabot update sources to use the organisation’s type: dependencies label, including security updates.
• Remove redundant target-branch overrides so Dependabot uses the default branch while applying the configured labels consistently.

[sourcery-ai]

Reviewer's Guide

Configuration

Add the organisation’s dependency label to each Dependabot update entry and remove target-branch so the options also apply to security updates.

• .github/dependabot.yml L2-37 (7 small edits)

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (c123f05) to head (dc93543).

Additional details and impacted files

@@            Coverage Diff            @@
##               dev      #301   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines          422       422           
=========================================
  Hits           422       422           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sourcery-ai]

Linked issues

Checked at commit dc93543

#300 ci: let Dependabot label all its pull requests · 3 of 4 met · 1 to check by hand

#	Requirement	Status	Notes
1	No entry or group sets target-branch.	✅ Met
2	Every updates entry sets labels: ["type: dependencies"].	✅ Met
3	Nothing else in the file changes, apart from the comment.	✅ Met
4	Dependabot pull requests opened afterwards, security updates included, carry only type: dependencies.	👀 Check by hand (external system)	After merging, verify that Dependabot-created version and security update pull requests carry only the type: dependencies label.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Needs a human reviewer. If the configuration is wrong, Dependabot pull requests may get an incorrect label or target branch; the affected PRs can be corrected individually. Reverting stops the behavior on future PRs, but does not remove labels already applied.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook