Skip to content

chore: add dependabot.yml (pip / github-actions / docker)#18

Closed
cmeans-claude-dev[bot] wants to merge 1 commit into
mainfrom
chore/dependabot-config
Closed

chore: add dependabot.yml (pip / github-actions / docker)#18
cmeans-claude-dev[bot] wants to merge 1 commit into
mainfrom
chore/dependabot-config

Conversation

@cmeans-claude-dev

Copy link
Copy Markdown
Contributor

Summary

Replaces the GitHub starter skeleton with a real Dependabot config tailored to this repo. Tracks weekly version updates across the three ecosystems present in tree:

  • pip at /pyproject.toml + uv.lock (PyYAML, pypinfo, and the dev extras: pytest, pytest-cov, ruff, mypy, types-PyYAML).
  • github-actions at / — workflow files under .github/workflows/ (CI matrix, publish workflows, label automation).
  • docker at /deploy/docker — Dockerfile base image for the optional containerized deployment shape.

Schedule is weekly, Monday 06:00 America/Chicago — keeps PR volume manageable for a solo project. Each ecosystem groups its updates into a single weekly PR (instead of one PR per dep) to keep notification noise down.

Labels (dependencies plus a per-ecosystem qualifier) are applied only if those labels already exist; Dependabot does not auto-create labels. The label-automation workflows continue to drive the QA-flow labels separately.

CHANGELOG entry omitted — repo infrastructure, not a user-visible product change (consistent with how PR #17's community-health files are landing).

Test plan

  • After merge, Dependabot should post an "Initial setup" PR within ~10 min (or on the next Monday at 06:00 CT) — verify it lands and runs the normal CI matrix.
  • Confirm Settings → Code security and analysis → Dependabot shows version updates as enabled.
  • Confirm the three ecosystems are recognized — visit Insights → Dependency graph → Dependabot and check each shows last-updated timestamps.
  • First-week PRs apply the configured labels (or, if any of dependencies/python/github-actions/docker aren't yet defined, the missing labels are silently skipped — this is expected and not a regression).
  • Generated commit messages start with chore(deps) prefix.

Tracks weekly updates across the three ecosystems this repo touches:

- pip: runtime + dev deps in pyproject.toml (also picks up uv.lock so
  the version bumps stay reproducible). Covers PyYAML, pypinfo, and
  the dev extras (pytest, pytest-cov, ruff, mypy, types-PyYAML).
- github-actions: workflow files under .github/workflows/ (CI matrix,
  publish workflows, label automation).
- docker: deploy/docker/Dockerfile base image.

Schedule is weekly (Monday 06:00 America/Chicago) to keep PR volume
manageable for a solo project. Each ecosystem groups its updates into
a single PR per week (instead of one PR per dep) so notification
noise stays low. Labels (dependencies + per-ecosystem qualifier) are
applied only if they already exist on the repo; Dependabot does not
auto-create labels.

CHANGELOG entry omitted — repo infrastructure, not user-visible.
@github-actions github-actions Bot added the Awaiting CI Dev complete, waiting for CI/Codecov to pass before QA label Apr 25, 2026
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@github-actions github-actions Bot added Ready for QA Dev work complete — QA can begin review and removed Awaiting CI Dev complete, waiting for CI/Codecov to pass before QA labels Apr 25, 2026
@cmeans-claude-dev

Copy link
Copy Markdown
Contributor Author

Closing — CreateEvent leak under v1 bot-push design (first push of chore/dependabot-config was attributed to cmeans instead of the bot). Force-push does not fix this — CreateEvent actor is immutable.

Replaced by #21 with the v2 bot-push design active (CreateEvent now attributes to cmeans-claude-dev[bot]). Same commit cherry-picked; branch contents identical.

Background: cmeans/claude-dev#4 deployed v2.

@cmeans-claude-dev cmeans-claude-dev Bot deleted the chore/dependabot-config branch April 26, 2026 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Ready for QA Dev work complete — QA can begin review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant