Skip to content

Correct Dependabot dependency grouping - #1001

Open
sehkone wants to merge 1 commit into
mainfrom
sehkone/issue-1000
Open

sehkone wants to merge 1 commit into
mainfrom
sehkone/issue-1000

Conversation

@sehkone

@sehkone sehkone commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Summary

Dependabot classifies all Cargo and GitHub Actions dependencies as production, so the development groups introduced by #168 cannot receive updates. Replace each ecosystem's production/development pairs with one minor/patch version-update group and one security-update group, without dependency-type filters.

Major version updates remain ungrouped, and security updates retain no semantic-version restriction. Weekly schedules, labels, PR limits, directory settings, and the entire Docker entry are unchanged. Only .github/dependabot.yml changes; no release-note entry is needed for this repository maintenance correction.

Closes #1000

Validation

  • Passed YAML parsing and validation against the Dependabot v2 JSON schema.
  • Passed parsed before/after comparison: exactly the intended Cargo and GitHub Actions groups changed; all other settings are identical.
  • Rebased onto main at 215eb13601406a389172e996ad1b0880864532ca, which includes the merged rustls security fix from Update rustls to fix TLS handshake validation #1003. Confirmed the Dependabot file is byte-for-byte identical to the version validated before the rebase and the lockfile matches updated main.
  • cargo audit passed after the rebase; the existing non-fatal unmaintained rustls-pemfile warning remains.
  • git diff --check passed; the final PR diff still changes only .github/dependabot.yml.
  • Local full preflight and Docker matrix are exempt under AGENTS.md: this Dependabot-only change affects no Docker lifecycle, E2E scripts, or application code paths. Full PR CI remains enabled and runs again for the rebased commit.

Hosted Dependabot PR generation can only be observed after this configuration reaches the default branch and eligible updates exist; schema validation does not exercise that scheduler.

Cargo and GitHub Actions classify all dependencies as production, so
separate development groups never receive updates. Use one minor/patch
version group and one unrestricted security group for each ecosystem.

Closes #1000

@octoaide octoaide Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall: patch is correct — The patch correctly removes unsupported dependency-type distinctions while preserving minor/patch grouping, unrestricted security grouping, major-update eligibility, and all unrelated Dependabot settings. The configuration is valid and the PR checks pass.

No findings that block this change.

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.

Correct ineffective Dependabot dependency groups

1 participant