Repository navigation
chore(deps): migrate dependency updates to Renovate - #5
Merged
Merged
Conversation
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.
What
Opts this repository into the organization Renovate preset (
github>AgentsKit-io/.github).mainin this repository.Why
Maintainer decision (2026-10-03): replace Dependabot version updates with one central Renovate preset. Grouped updates cut the per-package PR fan-out that was saturating CI runners.
How
The preset schedules updates on Mondays (America/Sao_Paulo), waits 3 days after npm releases, groups dev and production patch/minor updates, keeps majors separate for review, and auto-merges only development patch/minor and GitHub Actions updates after required checks pass. Dependabot security alerts stay enabled; they are separate from version-update config.
Validation
renovate-config-validator --strictpasses.