Skip to content

chore(renovate): disable renovate; dependabot owns updates - #233

Merged
ChelseaKR merged 1 commit into
mainfrom
chore/renovate-scope
Sep 18, 2026
Merged

ChelseaKR merged 1 commit into
mainfrom
chore/renovate-scope

Conversation

@ChelseaKR

Copy link
Copy Markdown
Owner

What

Turns Renovate off in this repo ("enabled": false) and adds a one-line description explaining why. .github/dependabot.yml is unchanged.

Why

The Renovate app was just installed here. With config:recommended it would open PRs for the same pip and github-actions dependencies Dependabot already updates, so every bump would show up twice. The agreed split is that Dependabot owns all dependency and version updates, and Renovate only bumps the vendored portfolio-standards pin through a regex customManager.

This repo doesn't have that customManager, so Renovate has nothing left to do here. It's a ci-fetch consumer: the standards pin is the ref: v1.0.1 on the actions/checkout step in .github/workflows/standards.yml, kept in lockstep with the root .standards-version. No Renovate manager bumps that pin today, and neither does Dependabot.

The codeql-action grouping rule is gone along with the rest. It only applied to Renovate's github-actions manager, and dependabot.yml already has its own codeql-action group.

Checks

  • renovate-config-validator --strict (Renovate 44.97.6, repo mode) passes.
  • Local dry run (--platform=local --dry-run=extract) now ends with Repository result: disabled-by-config.
  • Renovate hadn't opened any PRs, renovate/* branches, or a Dependency Dashboard issue here yet, so there are no duplicates to close.

What Renovate covered that Dependabot doesn't

dependabot.yml only declares pip and github-actions. The before-change dry run shows Renovate's defaults also tracked the files below. After this PR, none of them are tracked automatically:

  • infra/Dockerfile: the digest-pinned python:3.12-slim base. The Dockerfile comment says "Renovate tracks this digest and opens a PR when it moves", which is no longer true.
  • infra/aws/docker-compose.deploy.yml: caddy
  • infra/aws/terraform/versions.tf: the aws provider and hashicorp/terraform
  • tools/a11y_browser/package.json: @axe-core/playwright, @playwright/test
  • .python-version

A few docs also describe Renovate as active: README.md ("Dependabot + Renovate"), docs/DORA-DELIVERY-HEALTH-REVIEW.md ("renovate.json now handles Actions digest pinning"), and the .pre-commit-config.yaml header. Restoring the Dockerfile, compose, terraform, and npm coverage would mean adding docker, terraform, and npm entries to dependabot.yml. That's a separate decision.

Prepared with AI assistance; reviewed before submission.

This repo has no portfolio-standards customManager, so Renovate has
nothing to do that Dependabot does not already do. enabled: false stops
it opening PRs that duplicate Dependabot's updates.
@ChelseaKR
ChelseaKR merged commit d74744e into main Sep 18, 2026
17 checks passed
@ChelseaKR
ChelseaKR deleted the chore/renovate-scope branch September 18, 2026 13:42
ChelseaKR added a commit that referenced this pull request Sep 18, 2026
…ping (#234)

Renovate was disabled here in #233. A Renovate extract dry run of main
with config:recommended shows it also tracked files no Dependabot entry
covers: the digest-pinned python base in infra/Dockerfile, the caddy
image in infra/aws/docker-compose.deploy.yml, the AWS provider in
infra/aws/terraform, and the npm harness in tools/a11y_browser. Add
docker, docker-compose, terraform and npm entries for them in this
file's existing style (weekly, limit 5, dependencies label, build
prefix).

The compose entry ignores the locally built `ledger` image, which
Dependabot would otherwise try to look up on Docker Hub.

infra/Dockerfile no longer says Renovate tracks the digest. The pins
Dependabot cannot update (.python-version, setup-* version inputs)
are listed in dependabot.yml as a manual check.
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.

1 participant