From ac92ddde65c1fc0ec814721cfecb09c88ae78614 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 14 Aug 2026 15:26:17 +0000 Subject: [PATCH] chore: run the Renovate validator unpinned, and quiet npm's warnings Two changes to the same step, both about noise rather than correctness. The validator no longer pins its own version. Renovate opened a pull request every time it released, which is a lot of traffic for a linter we do not ship, and the newest release is the one that knows about the newest deprecations anyway. The tools whose versions actually affect the build stay pinned. NPM_CONFIG_LOGLEVEL=error silences npm's "npm warn deprecated ..." lines. Those come from packages deep inside Renovate's own dependency tree, not from this repository's config, but they print directly above the validator's output and read as if the config were the thing being called deprecated. The config itself validates clean. --- .github/workflows/config-validation.yml | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/.github/workflows/config-validation.yml b/.github/workflows/config-validation.yml index 2b11487..cc32e8b 100644 --- a/.github/workflows/config-validation.yml +++ b/.github/workflows/config-validation.yml @@ -55,11 +55,19 @@ jobs: # config files itself and validates them as repository config; passing a # path instead makes it validate them as global config, which is a # different and weaker set of rules. + # + # Deliberately unpinned. This is a linter for our config, not something we + # ship, and the newest release is the one that knows about the newest + # deprecations. Its own version is not worth a pull request. + # + # NPM_CONFIG_LOGLEVEL: npm prints "npm warn deprecated ..." for packages + # deep inside Renovate's own dependency tree. Those say nothing about the + # config being validated, and reading them as if they did is the obvious + # mistake to make when they appear directly above the validator's output. - name: Validate Renovate config env: - # renovate: datasource=npm depName=renovate - RENOVATE_VERSION: "44.28.0" - run: npx --yes --package "renovate@${RENOVATE_VERSION}" -- renovate-config-validator --strict + NPM_CONFIG_LOGLEVEL: error + run: npx --yes --package renovate -- renovate-config-validator --strict # The validator above accepts a well-formed pattern that matches nothing, # so this covers the gap it leaves.