<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Automation on johanneskueber.com</title><link>https://johanneskueber.com/tags/automation/</link><description>Recent content in Automation on johanneskueber.com</description><generator>Hugo</generator><language>en_US</language><lastBuildDate>Tue, 26 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://johanneskueber.com/tags/automation/index.xml" rel="self" type="application/rss+xml"/><item><title>Signed Dependency Updates with Renovate and Gitea</title><link>https://johanneskueber.com/posts/2026-05-26-sign-renovate-commits/</link><pubDate>Tue, 26 May 2026 00:00:00 +0000</pubDate><guid>https://johanneskueber.com/posts/2026-05-26-sign-renovate-commits/</guid><description>&lt;p&gt;Keeping dependencies up to date is one of those chores that is easy to neglect and expensive to ignore. Renovate solves it nicely: it scans my repositories, opens pull requests for outdated dependencies, and - if I let it - merges them on its own. On a self-hosted Gitea instance with branch protection, however, there is a catch. If I require signed commits on my protected branches, an unsigned bot commit is simply rejected. So before automating anything, Renovate needs an identity and a signing key, and its commits need to show up as &lt;em&gt;Verified&lt;/em&gt;.&lt;/p&gt;</description></item></channel></rss>