Use cases
Dependency upgrades that finish
Dependabot and Renovate open the pull requests. The part nobody has time for — waiting for CI, chasing the one failing job, merging the eleven that are fine — is the part we run.
Pull request #731
Handle expired workspace tokens
+ if (token.expiresAt < Date.now()) {
+ await rotateWorkspaceToken(token)
+ }The bottleneck is not opening the PR
Automated bump PRs are easy to create and expensive to finish. developerz.ai recognises Dependabot and Renovate as bots and deliberately does not reply to them — no bot-on-bot threads. What it does instead is watch each PR through your existing checks, re-run what is worth re-running, and merge on your policy once CI, review and your branch protections agree. Anything that stays red comes to you with the failing job attached.
No bot-on-bot noise
Dependabot and Renovate PRs are detected and never answered with another bot comment — they are treated as work, not as conversation.
Gates stay machines
A bump merges when CI is green, review passes and your branch protections allow it. Not because something decided it looked safe.
The stuck ones surface
A PR that will not go green stops being invisible: it is escalated with the failing job, not left to rot behind forty others.
Go deeper
Set the rules in one file
Which paths auto-merge, which always wait for a human, which are ignored entirely — it is all one committed policy file.
Read the .maintainer.yml referencePut a fleet of AI developers to work
Bring your own keys and your own boxes, drop a .maintainer.yml, and let the loops run — audited end to end. Access is invite-only.