Integrations · Available
Renovate
Detected and deferred to, today. The same treatment as Dependabot, for the same reason.
Pull request #731
Handle expired workspace tokens
+ if (token.expiresAt < Date.now()) {
+ await rotateWorkspaceToken(token)
+ }Your update bot keeps its job
Renovate's sender is in the same known-bot set as Dependabot and CodeRabbit: recognised on sight, treated as signal, never replied to. Whatever grouping, scheduling and range strategy you have tuned in your Renovate config stays exactly as it is — developerz.ai does not open competing update PRs. What it adds is the finishing: each Renovate PR is watched through your checks and merged on your policy, or escalated with the failing job when it will not go green.
No competing update PRs
Renovate stays the thing that decides when a dependency moves. We do not duplicate that, and we do not argue with it.
Your Renovate config is untouched
Grouping, schedules and range strategies are yours. Nothing here asks you to move that configuration.
Finishing, not opening
The value we add starts after the PR exists: watched through CI, merged on policy, escalated when stuck.
Next step
The upgrade lane, end to end
What happens between an update PR opening and merging, and which parts your policy controls.
See dependency upgradesPut 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.