Skip to content

chore: add the shared DIRACGrid Renovate config preset - #7

Merged
aldbr merged 3 commits into
DIRACGrid:mainfrom
fstagni:renovate-preset
Nov 16, 2026
Merged

aldbr merged 3 commits into
DIRACGrid:mainfrom
fstagni:renovate-preset

Conversation

@fstagni

@fstagni fstagni commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Part of #5.

Adds renovate-config.json, the org-wide Renovate baseline, so that per-repo renovate.json files stop copy-pasting the same policy:

  • config:recommended + helpers:pinGitHubActionDigests (digest pinning of GitHub Actions, which zizmor's unpinned-uses audit asks for; the pins keep receiving updates) + :configMigration (PRs that migrate deprecated options such as matchPackagePatterns and fileMatch)
  • minimumReleaseAge: 7 days (supply-chain cooldown for direct dependencies). DIRACGrid's own Actions, reusable workflows and ghcr.io/diracgrid images are exempt: refs pinned to a branch (@<sha> # main) have no release timestamp and would otherwise never get a digest update.
  • GitHub Actions updates grouped in one PR, labelled dependencies + github-actions
  • weekly lock file maintenance: one "Lock file maintenance" PR per repo, covering pixi.lock whether it comes from pixi.toml or [tool.pixi] in pyproject.toml
  • Renovate defaults otherwise: majors in their own PR per dependency, nothing automerges

About cooldowns and lock files. Lock file maintenance re-resolves every dependency to its newest version and does not apply minimumReleaseAge. The cooldown for transitive dependencies therefore has to come from pixi: set exclude-newer = "7d" in the workspace (diracx and DIRACOS2 already do). npm has no rolling equivalent, so npm lock files are not refreshed blindly.

A CI job validates the preset with renovate-config-validator --strict, because a broken preset breaks Renovate in every repo at once.

Repos adopt it with a one-liner:

{
  "extends": ["local>DIRACGrid/.github//renovate-config"]
}

Repos with maintained release branches (DIRAC, WebAppDIRAC) also set "baseBranchPatterns": ["$default", "/^rel-/"].

Follow-up PRs will migrate the repos that already use Renovate (diracx, diracx-web, diracx-charts, DIRACOS2, intercede, signurlarity) to this preset; merge this one first: until it lands on main, those references cannot resolve.

- Rename renovate-config.json5 to renovate-config.json: Renovate appends
  ".json" to a preset name without extension, so the documented
  `local>DIRACGrid/.github//renovate-config` never found the .json5 file.
- Drop the pixi-only lockFileMaintenance group: the pep621 manager also
  refreshes pixi.lock (via [tool.pixi]), so the group split one refresh
  into two PRs (diracx#1174 and #1175 touch the same pixi.lock).
- State that lock file maintenance skips minimumReleaseAge; the cooldown
  for transitive deps is pixi's `exclude-newer = "7d"`. Do not refresh
  npm lock files, which have no rolling equivalent.
- Exempt DIRACGrid's own Actions, reusable workflows and images from the
  cooldown: refs pinned to a branch have no timestamp and were blocked
  forever under timestamp-required.
- Drop the "Major version updates" group (it bundled every major in one
  PR; Renovate already separates majors per dependency) and the no-op
  automerge: false rules (they also overrode a repo-level automerge).
- Use labels + addLabels so rules add labels instead of replacing them.
- Add :configMigration, and a workflow validating the preset as repo
  config, since every repo breaks at once if it is invalid.

Assisted-by: Claude:claude-opus-5-5
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