AIToday
Large Language ModelsAI Coding AssistantsZenn AI/MLPublished: Oct 9, 2026, 10:00 JST

Renovate: AI Reviews Pull Requests, Auto-Merge Enabled

Renovate: AI Reviews Pull Requests, Auto-Merge Enabled

3 Key Points

  1. What happened

    A developer built a GitHub Actions workflow where Claude Code reviews Renovate's major and minor pull requests, assigning verdicts approve, changes_required, or human_review, then auto-merges approved ones if tests pass.

  2. Why it matters

    It targets minor updates for auto-merge while major updates still require human sign-off, easing the PR backlog without handing AI full control.

WHO IT HITSEngineering teams using Renovate face a growing backlog of minor and major dependency PRs; this workflow lets them delegate review to an AI agent while keeping major-version merges manual.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The workflow reflects a practical response to a common pain point: while tools like Dependabot and Renovate already automate creating update pull requests, the review step remains manual. Reading release notes to check for breaking changes, deprecated APIs, and type or config impacts can eat minutes per PR, and those minutes add up as the queue grows. The author splits updates by type: patches continue to auto-merge after CI passes, minor updates go through AI review with possible auto-merge, and major updates are reviewed but left for a person to merge. Packages like Rails that can include de facto breaking changes in minor releases are handled the same as major updates. To keep AI use efficient, the workflow computes a SHA-256 fingerprint from only the added and removed lines of the diff. If a rebase leaves the change content the same, the previous verdict is reused rather than triggering a fresh review. The design also separates the AI review job from write permissions, so even if malicious instructions are hidden in release notes or node_modules, the agent cannot post comments or commit. The prompt explicitly warns against following instructions found in those files, a defense against prompt injection. Auto-merge is off by default, letting teams compare AI verdicts with their own judgment before enabling it.

FAQ
Which dependency updates can the AI agent auto-merge?
The AI agent auto-merges only minor updates when it returns an approve verdict, CI checks pass, and a deps-ai-review:manual-merge label is absent. Major updates show results only and are merged by a person.
How do I turn off auto-merge if the AI reviews incorrectly?
Auto-merge is controlled by the DEPS_AI_REVIEW_AUTO_MERGE variable, which is off by default. Removing the variable stops auto-merge immediately, serving as an emergency brake.
How does the system avoid wasting AI calls on rebased PRs?
It computes a fingerprint from the changed lines of the diff. If the fingerprint matches the previous review, it reuses the earlier verdict instead of calling the AI agent again.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleHex cuts wrong edits 7x with evals on Quick Edits