Separate Dependabot uv grouping for dev and prod dependencies

[Copilot]

What?

Split uv dependency grouping into separate dev and prod groups with different update policies.

Why?

Dev dependencies can safely accept major version bumps grouped together, while prod dependencies should remain conservative with only minor/patch grouping.

Changes:

• Replace single python-minor-patch group with two distinct groups:
  • uv-dev: Groups development dependencies with major, minor, and patch updates
  • uv-prod: Groups production dependencies with minor and patch updates only

groups:
  uv-dev:
    patterns:
      - "*"
    dependency-type: "development"
    update-types:
      - "major"
      - "minor"
      - "patch"
  uv-prod:
    patterns:
      - "*"
    dependency-type: "production"
    update-types:
      - "minor"
      - "patch"

Testing:

Validated YAML syntax.

References:

• Dependabot grouping configuration docs

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Dependabot uv grouping (dev & prod)</issue_title>
<issue_description>Dependabot currently groups minor & patch dependencies. I would like to separate out the grouping of dev dependencies from prod dependencies, however. We should therefore create two groups, one for uv dev dependencies and one for uv prod dependencies. Dev dependencies should combine major versions as well as minor and patch, whereas prod major dependencies shouldn't be grouped with minor and patch bumps.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Dependabot uv grouping (dev & prod) #17

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.