Dependency Updates That Arrive Tested
On a schedule you set, an agent updates your libraries, runs the tests, and opens a pull request, so updates arrive ready to review.
Updates Pile Up Until They're a Project
Small version bumps are easy to put off, and they add up. Automated update tools open the pull request, but when an update breaks a test or needs a code change, the work lands back on an engineer. Skipped updates turn into a large, risky upgrade later.
An Agent Does the Update and the Follow-Up
Schedule an agent to update dependencies, run the tests, and propose any code changes the update needs. Ask for a pull request with the changes and test results, then review it like any other PR.
- "@tanstack/react-query": "5.59.0",
+ "@tanstack/react-query": "5.62.0",
- "zod": "3.23.8",
+ "zod": "3.24.1",
Tests passed, PR opened
Common Questions
How often does it run?
Choose a recurring cron schedule, such as nightly or weekly, run it once at a chosen date and time, or start the agent by hand.
What happens when an update breaks the tests?
Ask the agent to investigate the failure, propose a fix if it can, and report any unresolved issues.
Does it merge updates automatically?
Keep merging under human control. Ask for a pull request and require human approval before it merges.
Which models can it use?
Any major provider, plus local and private models. Bring your own keys or subscription, and there's no markup on tokens.
Related: Automations docs, Security patches.
Keep Your Attention for the Hard Problems
Start with one repo and one recurring task.