Add Renovate dependency updates#17
Merged
Merged
Conversation
Renovate is now the dependency-update path used by roborev, and kit should follow the same workflow instead of relying on Dependabot-style configuration. Keeping the managers explicit limits automated PRs to the dependency surfaces this repo actually has today: pinned GitHub Actions and Go modules. Go dependency updates are grouped and run through gomodTidy so generated PRs are easier to review and leave module metadata consistent. Vulnerability alerts stay immediate while normal updates retain the release-age buffer from the roborev config. Validation: jq . renovate.json Generated with Codex Co-authored-by: Marius van Niekerk <mariusvniekerk@users.noreply.github.com>
The base Renovate migration intentionally mirrors the current Go and GitHub Actions surfaces, but kit is expected to carry JavaScript dependency metadata separately. Enabling Renovate's npm manager in a follow-up keeps that concern reviewable on its own while allowing package.json, pnpm, npm, and Yarn lockfile updates to be handled by Renovate when those files are present. Grouping JavaScript dependency updates keeps the generated dependency-bump PR stream aligned with the grouped Go update behavior instead of producing one PR per package by default. Validation: jq . renovate.json Generated with Codex Co-authored-by: Marius van Niekerk <mariusvniekerk@users.noreply.github.com>
roborev: Combined Review (
|
mariusvniekerk
changed the title
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
1 participant
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
roborev has moved dependency-update automation to Renovate, so kit should use the same mechanism for its reusable library dependencies instead of depending on a Dependabot-style workflow. This config keeps Renovate scoped to GitHub Actions, Go modules, and JavaScript package metadata.
Normal dependency updates keep the same review-friendly release-age buffer as roborev, while vulnerability alerts are allowed through immediately. Go module updates are grouped and run with
gomodTidyso automated PRs leave module files consistent. JavaScript dependency updates are also grouped through Renovate’s npm manager, which coverspackage.jsonplus npm, pnpm, and Yarn lockfile maintenance when those files are present.I checked the current kit tree and current
origin/*branches; there is no JavaScript manifest or lockfile yet, so the JavaScript manager is config-only until that stack lands.Validation
jq . renovate.jsonmain; checks may rerun after this base change.