Repository navigation
chore(renovate): track pre-commit hook revisions - #461
DevSecNinja wants to merge 1 commit into
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues were identified for the Renovate pre-commit dependency tracking changes.
No open issues 🎉
What changed in this PR
Adds Renovate tracking for hadiscover’s pre-commit dependencies, addressing the coverage gap in #460.
Changes:
- Enables the built-in
pre-commitmanager to track the 13 hook revision pins. - Adds a custom regex manager for npm
additional_dependencies, covering the pinned Biome package.
| File | Description |
|---|---|
renovate.json5 |
Enables hook revision updates and adds npm dependency tracking for pre-commit configuration. |
Review effort: Balanced
Description
Renovate's
pre-commitmanager is off by default, so the hook revisions in.pre-commit-config.yamlwere never updated.Changes
renovate.json5: enable thepre-commitmanager for the 13rev:pins.renovate.json5: a custom manager for npm packages inadditional_dependencies(the built-in manager only updates Python ones), which covers@biomejs/biome@2.3.10.Expect a first batch of hook updates after merge; non-major ones land in the weekly group, major ones in their own PRs.
Closes #460
Checklist
mise exec -- lefthook run pre-commit)Validation (static and API-only; the repo was not cloned and nothing was executed in it): changed JSON5
files parse, and every new or affected Renovate regex was run (in Python, with RE2/JS named groups
translated) against the files on
main. Each matches exactly the lines listed above.renovate-config-validatorwas not run (the npm registry is blocked on the authoring machine). Renovatevalidates the config on its next run and reports problems on the Dependency Dashboard.
Summary by CodeRabbit