<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Debugging on secustor</title><link>https://secustor.dev/tags/debugging/</link><description>Recent content in Debugging on secustor</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 07 Sep 2026 00:06:24 +0200</lastBuildDate><atom:link href="https://secustor.dev/tags/debugging/index.xml" rel="self" type="application/rss+xml"/><item><title>Renovate: It was a packageRule all along</title><link>https://secustor.dev/blog/renovate_config_debugger/</link><pubDate>Mon, 07 Sep 2026 00:06:24 +0200</pubDate><guid>https://secustor.dev/blog/renovate_config_debugger/</guid><description>&lt;p&gt;As a Renovate maintainer, the question I answer most often is not &amp;ldquo;why is Renovate broken?&amp;rdquo; but &amp;ldquo;why did Renovate do that with my config?&amp;rdquo;.
The honest answer is usually &amp;ldquo;because you configured it that way&amp;rdquo;, and finding out where is the hard part.
Every one of these mysteries ends the same way: you pull off the mask, and it was a packageRule all along.
The &lt;a href="https://renovate.secustor.dev/"&gt;Renovate Config Debugger&lt;/a&gt; is my attempt to make that answer visible before Renovate runs.&lt;/p&gt;</description></item></channel></rss>