Renovate CLI
Renovate CLI brings dependency updates across ecosystems into pull requests governed by the team’s rules and schedule.
- 23,034 ★ on the repository
- Last commit
- AGPL-3.0
Extended access
Why this level
- Repository-authorized runs create branches and change dependencies; incorrect rules can propose unwanted updates.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/renovate-cliDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Repository-authorized runs create branches and change dependencies; incorrect rules can propose unwanted updates.
This is third-party code. Review the repository files before installing.
What it does
Renovate CLI discovers dependency manifests, looks up new versions in registries and prepares changes on separate branches. The team receives a pull request with changed files and project check results. Supported ecosystems include npm, Python, Go, Docker and .NET. Pull requests can include Mend’s release-age, adoption and passing-test metrics. Mend collects update data from users of its Renovate app. Teams use those signals alongside their own tests of application compatibility.
Who it is for. Repository maintenance teams reviewing dependency updates in pull requests and testing them in CI.
Good fit when
- A repository mixes ecosystems and the team misses some new releases.
- Maintainers review dependency changes in pull requests alongside CI results.
- A project uses a private registry reachable from its own infrastructure.
- The team moves manual version discovery into a recurring CI job.
Not a fit when
- The team intends to accept updates without compatibility tests.
- The token may not create branches or pull requests.
- The infrastructure has no CI job or scheduler for recurring CLI runs.
Example request
Draft an update configuration for a test repository with required review and CI, without automatic merging.Limitations
The platform token needs access to selected repositories and permission to create branches and pull requests. Private registries separately require access to packages and version information; the repository token may not cover them. Run the standalone CLI through an external schedule or CI; one invocation does not provide continuing maintenance. Enable automatic merging with `automerge`. Set required tests in the branch rules so they must pass before a merge.
How to disable. Stop Renovate jobs and revoke its token if needed. Close existing pull requests separately; their branches also remain in the repository.
FAQ
Does Renovate change versions?
Yes. The CLI changes dependency files on separate branches and opens pull requests. The team accepts them under its repository rules.
Is a Mend server required?
No. The CLI runs on your infrastructure. Choose an npm package or Docker image in the [self-hosting guide](https://docs.renovatebot.com/getting-started/running/#available-distributions).
The repository is accessible, but a private package is missing?
Configure registry credentials through `hostRules`, matching its address with `matchHost`. Repository access and private-package access are separate checks.
Can automerge be limited to selected updates?
Enable `automerge` in selected `packageRules`. Keep manual merging where you want to inspect code changes, and configure required branch tests for automatically accepted updates.
Are ready-made CI integrations available?
Use the [official GitHub Action](https://github.com/renovatebot/github-action) or [GitLab Renovate Runner](https://gitlab.com/renovate-bot/renovate-runner/). Select the platform integration and configure job credentials and scheduling.
Discussion
No questions or reviews yet.
Related
CLI toolsAdditional Cargo commands update dependency requirements and package versions, with dry-run previews for agent review.
The CLI selects a project’s package manager and forwards short install and run commands to reduce confusion in agent workflows.
A local codebase index with ten MCP tools: dependency graph, git history, code health and architectural decisions without re-grepping on every step
A CLI that records coding-agent steps and links file lines to the tool call, conversation and original request behind them.
A CLI that reviews code changes, fixes confirmed findings and repeats review before deterministic repository verification.
The CLI manages Python projects, environments and package builds so agents can run repeatable repository-defined commands.
README in short
The README links to a GitHub Action and GitLab Runner for CI execution. Direct CLI execution is documented for custom jobs; the infrastructure owner supplies scheduling and credentials.