Dependency upgrade PRs that are fixed until tests pass
When a version bump breaks the build, an async agent updates the calling code and opens a PR with passing tests for review.
The use case
Bots like Renovate open version bump PRs, but breaking upgrades sit for weeks because someone has to fix the code. An async agent such as Google's Jules can take a task like 'upgrade this library and fix what breaks', clone the repo into a cloud VM, change the calling code, run tests, and show its plan and diff before opening a pull request. This turns a stale bump PR into something reviewable. A developer still reads the changelog for behavior changes the tests miss, reviews the diff, and merges. Major framework upgrades should be split into smaller steps.
Example workflow
- Let a bump bot open the version upgrade PR
- Hand failing bumps to the async agent with the error output
- Agent plans the fix, edits code and runs tests
- Review the plan, diff and library changelog
- Merge after normal review
Tools
- Jules
- Renovate
- GitHub
Risks and guardrails
- Tests may not cover changed library behavior
- Agent may pin or downgrade to dodge errors; check the lockfile
- New dependencies need license and security review
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Jules docs: jules.google/docs
- Renovate docs: docs.renovatebot.com
- Jules extension (official page): github.com/gemini-cli-extensions/jules (checked 2026-11-19)
- GitHub MCP server (official page): github.com/github/github-mcp-server (checked 2026-11-09)