<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on Coderrob</title><link>https://coderrob.com/tags/security/</link><description>Recent content in Security on Coderrob</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 18 May 2026 00:00:00 -0500</lastBuildDate><atom:link href="https://coderrob.com/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Dependabot Configuration That Does Not Hate You Back</title><link>https://coderrob.com/posts/dependabot-configuration-grouping-cooldown-ecosystems/</link><pubDate>Mon, 18 May 2026 00:00:00 -0500</pubDate><guid>https://coderrob.com/posts/dependabot-configuration-grouping-cooldown-ecosystems/</guid><description>&lt;p>Dependabot is one of those tools that can either quietly keep your dependencies moving or bury your team under a pile of tiny pull requests.&lt;/p>
&lt;p>The difference is configuration.&lt;/p>
&lt;p>Out of the box, Dependabot tends to think in very small units:&lt;/p>
&lt;ul>
&lt;li>one dependency&lt;/li>
&lt;li>one update&lt;/li>
&lt;li>one pull request&lt;/li>
&lt;li>repeat until morale improves&lt;/li>
&lt;/ul>
&lt;p>That is fine for a small repo with three dependencies and the emotional complexity of a toaster. It is less fine for real projects with application packages, GitHub Actions, Docker images, Terraform modules, dev tooling, lockfiles, and a CI bill that starts to look like it has hobbies.&lt;/p></description></item></channel></rss>