From f55e857703b2a3875654d48860c0b781bc6cedf9 Mon Sep 17 00:00:00 2001 From: Federico Stagni Date: Tue, 17 Nov 2026 13:24:13 +0100 Subject: [PATCH 1/2] chore: enable Renovate's pre-commit manager in the shared preset Renovate disables the pre-commit manager by default, so the hook revs pinned in .pre-commit-config.yaml never get update PRs. Several repos still pin 2023-era hooks (black 23.1.0, flynt 0.77, pyupgrade v3.3.1) that predate the removal of ast.Str in Python 3.12 and crash on the current runner Pythons. Repos where the pre-commit.ci app already does the autoupdates (diracx, diracx-charts) disable this per-repo to avoid duplicate update PRs. Part of DIRACGrid/.github#5. --- renovate-config.json | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/renovate-config.json b/renovate-config.json index 353005a..4e67c5c 100644 --- a/renovate-config.json +++ b/renovate-config.json @@ -12,6 +12,13 @@ ], "labels": ["dependencies"], "minimumReleaseAge": "7 days", + "pre-commit": { + "description": [ + "Off by default in Renovate; without this, the hook revs pinned in .pre-commit-config.yaml never get update PRs.", + "Repos where the pre-commit.ci app already does the autoupdates (e.g. diracx) disable this per-repo to avoid duplicate PRs." + ], + "enabled": true + }, "lockFileMaintenance": { "enabled": true }, From 22fdd9c2f94c0dbbc212875bce3c304983c682aa Mon Sep 17 00:00:00 2001 From: aldbr <19813740+aldbr@users.noreply.github.com> Date: Tue, 17 Nov 2026 14:12:10 +0100 Subject: [PATCH 2/2] chore: group pre-commit hook updates and unblock branch-pinned Actions - one grouped PR for all pre-commit hook updates instead of one per hook - digest updates of third-party Actions pinned to a branch (e.g. pypa/gh-action-pypi-publish # release/v1) have no release timestamp, so minimumReleaseAge held them forever; let them through while versioned refs keep the cooldown Assisted-by: Claude:claude-opus-5-5 --- renovate-config.json | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/renovate-config.json b/renovate-config.json index 4e67c5c..4236f48 100644 --- a/renovate-config.json +++ b/renovate-config.json @@ -34,6 +34,19 @@ "groupName": "GitHub Actions", "addLabels": ["github-actions"] }, + { + "description": "Third-party Actions pinned to a branch (e.g. `pypa/gh-action-pypi-publish@ # release/v1`) have no release timestamp, so with the default `minimumReleaseAgeBehaviour` (timestamp-required) their digest updates would be held forever. Let them through; versioned refs (`# v4.2.0`) keep the cooldown.", + "matchManagers": ["github-actions"], + "matchUpdateTypes": ["digest"], + "matchCurrentValue": "!/^v?\\d/", + "minimumReleaseAgeBehaviour": "timestamp-optional" + }, + { + "description": "Group all pre-commit hook updates together, instead of one PR per hook.", + "matchManagers": ["pre-commit"], + "groupName": "pre-commit hooks", + "addLabels": ["pre-commit"] + }, { "description": "Lock file maintenance re-resolves everything to the newest version and skips minimumReleaseAge, so only the package manager can enforce a cooldown. pixi does it with `exclude-newer = \"7d\"` in pixi.toml / [tool.pixi.workspace] (set it in every pixi repo); npm has no rolling equivalent, so its lock files are not refreshed blindly.", "matchManagers": ["npm"],