Skip to content

chore(ci): extend dependabot to docs/ npm and Docker, group minor/patch bumps - #235

Open
BenjaminDEMAILLE wants to merge 3 commits into
mainfrom
chore/dependabot-coverage
Open

chore(ci): extend dependabot to docs/ npm and Docker, group minor/patch bumps#235
BenjaminDEMAILLE wants to merge 3 commits into
mainfrom
chore/dependabot-coverage

Conversation

@BenjaminDEMAILLE

Copy link
Copy Markdown
Contributor

Context

.github/dependabot.yml already existed and works (see the open chore(deps) PRs), but it watched only two ecosystems.

Gaps closed

  • docs/ (npm/pnpm) — the Astro Starlight site (docs/package.json, docs/pnpm-lock.yaml: astro, @astrojs/starlight, sharp) was never updated.
  • Docker — neither Dockerfile stage (rust:1-bookworm, debian:bookworm-slim) was tracked.

Noise reduction

Minor and patch updates are grouped into one PR per ecosystem per week. Major bumps deliberately stay ungrouped: they need a real review, and a grouped major is hard to bisect. open-pull-requests-limit is 5 per ecosystem (3 for Docker).

Per-ecosystem commit prefixes so the history stays readable: chore(deps) for cargo, chore(ci) for actions, chore(docs) for the site, chore(docker) for base images.

Verification

YAML parses and every group declares patterns: ["*"] plus explicit update-types. Config only: no source, workflow, or build change. GitHub validates the file on merge and reports problems in Insights > Dependency graph > Dependabot.

🤖 Generated with Claude Code

…p updates

The config watched cargo and github-actions only, so the Astro Starlight site
in docs/ (pnpm) and the two Dockerfile base images were never updated.

Minor and patch bumps are now grouped into one PR per ecosystem per week;
major bumps stay individual because they need review. Adds per-ecosystem
commit-message prefixes and open-pull-requests-limit to cut PR churn.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

@Zethson Zethson left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'd even be down for monthly & an open PR limit of like 1 to drastically reduce noise.

Review feedback: monthly schedule and open-pull-requests-limit 1 across all
four ecosystems, to cut update noise further. Security update PRs are exempt
from the limit and do not count toward it, so they still arrive immediately.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@BenjaminDEMAILLE

Copy link
Copy Markdown
Contributor Author

Done in 378a74f: monthly and open-pull-requests-limit: 1 on all four ecosystems.

Two consequences worth having on record:

  • Security updates are unaffected. Per the options reference, security update PRs are exempt from open-pull-requests-limit and do not count toward it, so a vulnerable dependency still gets a PR immediately rather than waiting for the monthly window.
  • Major bumps now queue. The limit counts all open version-update PRs for an ecosystem, so with the grouped minor/patch PR open, a major sits until that one is merged or closed. That is the intended trade for the quiet, just not invisible.

Rebased on main so the clippy 1.98 fix (#236) is included; CI should be green now.

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.

2 participants