<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Renovate on DevOps von UCLAB</title>
    <link>https://uclab.dev/tags/renovate/</link>
    <description>Recent content in Renovate on DevOps von UCLAB</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 02 Mar 2026 17:16:08 +0000</lastBuildDate>
    <atom:link href="https://uclab.dev/tags/renovate/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Automating Renovate PR Reviews with n8n</title>
      <link>https://uclab.dev/posts/automating-prs-with-n8n/</link>
      <pubDate>Mon, 02 Mar 2026 17:16:08 +0000</pubDate>
      <guid>https://uclab.dev/posts/automating-prs-with-n8n/</guid>
      <description>&lt;h2 id=&#34;the-problem-renovate-bot-is-prolific&#34;&gt;The Problem: Renovate Bot is Prolific&lt;/h2&gt;&#xA;&lt;p&gt;If you run a Kubernetes homelab with &lt;a href=&#34;https://docs.renovatebot.com/&#34;&gt;Renovate Bot&lt;/a&gt;, you know the drill. Every morning you wake up to a flood of open pull requests — patch updates, minor bumps, the occasional major version change. Each one needs a decision: safe to merge, needs a closer look, or definitely hands-off.&lt;/p&gt;&#xA;&lt;figure&gt;&lt;img src=&#34;https://uclab.dev/posts/automating-prs-with-n8n/images/gemini5.png&#34;&#xA;    alt=&#34;automation&#34;&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;Doing this manually gets old fast. But blindly auto-merging everything is a bad idea too — you really don&amp;rsquo;t want Renovate silently bumping your CloudNativePG major version at 2am.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
