chore: run the Renovate validator unpinned, and quiet npm's warnings - #93
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Twee wijzigingen aan dezelfde stap, allebei over ruis in plaats van correctheid.
Type of change
chore— maintenance (dependencies, config, CI/CD)De validator is niet langer gepind
Renovate opende een PR bij elke release van zichzelf. Dat is veel verkeer voor een linter die we niet meeleveren, en de nieuwste release is juist degene die de nieuwste deprecations kent.
De tools waarvan de versie wél invloed heeft op de build blijven gepind: Hugo, actionlint en lychee.
De "deprecated"-meldingen waren niet van de config
In het CI-log staan regels als:
Die
npm warn-regels komen van npm, over packages diep in Renovate's eigen dependency-tree. Ze zeggen niets over de config die gevalideerd wordt — maar ze staan direct boven de uitvoer van de validator, waardoor het lijkt alsof de syntax deprecated is. De config valideert schoon.NPM_CONFIG_LOGLEVEL=errorhaalt die regels weg.Lokaal niet reproduceerbaar gekregen (de waarschuwingen bleven hier uit, ook met een lege npm-cache — vermoedelijk een verschil in registry-route). De CI-run op deze PR is dus de eigenlijke bevestiging.
Checklist
hugo server— n.v.t.; in plaats daarvan is actionlint lokaal gedraaid en is de config metrenovate-config-validator --strict(44.30.1) gevalideerd🤖 Generated with Claude Code
https://claude.ai/code/session_01SwrLVfDhkTVHC945s1kZ2s
Generated by Claude Code